From: Digest <deadmail>
To: "OS/2GenAu Digest"<deadmail>
Date: Sat, 1 Nov 2008 00:00:50 AET-10EDT,10,1,0,7200,4,1,0,7200,3600
Subject: [os2genau_digest] No. 1735
Reply-To: <deadmail>
X-List-Unsubscribe: www.os2site.com/list/

**************************************************
Friday 31 October 2008
 Number  1735
**************************************************

Subjects for today
 
1  Re:  Connecting a Sony W910i to the internet : Wayne <datablitz at optusnet dot com dot au>
2  Re:  Connecting a Sony W910i to the internet : Ed Durrant <edurrant at durrant dot mine dot nu>
3  Re:  Connecting to NextG WAS Connecting a Sony W910i to the internet : Wayne <datablitz at optusnet dot com dot au>
4  Re:  Connecting a Sony W910i to the internet : Peter Moylan <peter at pmoylan dot org>
5  Re:  Connecting a Sony W910i to the internet : Peter Moylan <peter at pmoylan dot org>
6  Re:  Connecting a Sony W910i to the internet : Wayne <datablitz at optusnet dot com dot au>

**= Email   1 ==========================**

Date:  Fri, 31 Oct 2008 06:39:19 +0930
From:  Wayne <datablitz at optusnet dot com dot au>
Subject:  Re:  Connecting a Sony W910i to the internet

** Reply to note from Peter Moylan <peter at pmoylan dot org> Thu, 30 Oct 2008   
22:48:53 +1100 
 
On 30/10/08 22:18, Wayne wrote: 
    
>> As a test, I tried connecting under windoze using Injoy v3 (comes with 2    
>> NDIS drivers), success if drivers are installed, failed if not.  
    
>    
> The fact that the extra NDIS drivers are required in Windows is very  
> suggestive. As I recall it, NDIS files are plain text files that OS/2  also 
> uses. Thus, you might have some luck in installing those NDIS files  into 
> OS/2. 
>    
> --  Peter Moylan peter at pmoylan dot org http://www.pmoylan dot org 
>    
 
I found the 2 drivers but they are binary.  How would I attempt to install them? 
My test was done using XP. 
 
Relevant dirs:- 
fx 
    fx.sys 
    OemSeNT.inf  
    OemWin2k.inf 
fxdod 
    fxdod.sys 
    OemSeNT.inf  
    OemWin2k.inf 
 
Cheers 
Wayne


----------------------------------------------------------------------------------
 

**= Email   2 ==========================**

Date:  Fri, 31 Oct 2008 08:08:43 +1100
From:  Ed Durrant <edurrant at durrant dot mine dot nu>
Subject:  Re:  Connecting a Sony W910i to the internet

Wayne wrote:
> Hi all 
>  
> I have been trying for months to get this phone (ME) connected to the net via   
> Three using Injoy v3.  It seems to fail in the "handshaking" stage.  Could this   
> be due to ethernet?  Any suggestions welcome. 
>  
> Some relevant info:- 
>  
> This ME has ethernet capabilities (undocumented). 
> This ME has MSD capabilities (trapping). 
> Took the SIM card out & put it in the Samsung & it connected to Three   
> successfully (roaming charges apply). 
> As a test, I tried connecting under windoze using Injoy v3 (comes with 2   
> NDIS drivers), success if drivers are installed, failed if not. 
> I have a Samsung SGH-A501 connected to Telstra NextG successfully. 
> Emailed Injoy regarding this (no response). 
> Emailed Yahoo Injoy mailing list (didn't even appear on the list). 
>  
> No, I have no intention of accessing the internet using doze. 
>  
> Cheers 
> Wayne
>
>

>  

>
>   
Hi Wayne,

we may be able to help each other here. I have an LG working with 
"three" (you've probably seen my article in the voice newsletter from a 
few years back) - and yes since I've moved I also have to bear low speed 
and roaming charges if I use this. I have just got a Next-G Samsung 
SGH-A411 which I'm having a couple of issues with handshaking to Next-G.

You say you have your A501 working with Next-G - can you send me the 
config string details please ?

On the Sony - can you cut and paste the (trace on) messages from Injoy 
(in fact if you haven't already done so compare what you have set 
against what are in the screenshots in my article) - you might want to 
send all this info direct rather than on-list.

In case you don't have it - here's the reference to my article:

http://www.os2voice dot org/VNL/past_issues/VNL0606H/feature_1.html


Cheers/2
Ed.
----------------------------------------------------------------------------------
 

**= Email   3 ==========================**

Date:  Fri, 31 Oct 2008 12:05:06 +0930
From:  Wayne <datablitz at optusnet dot com dot au>
Subject:  Re:  Connecting to NextG WAS Connecting a Sony W910i to the internet

** Reply to note from Ed Durrant <edurrant at durrant dot mine dot nu> Fri, 31 Oct   
2008 08:08:43 +1100 
>    
> Wayne wrote: 
> > Hi all  
> >   
> > I have been trying for months to get this phone (ME) connected to the net   
via    
> > Three using Injoy v3.  It seems to fail in the "handshaking" stage.  Could   
this    
> > be due to ethernet?  Any suggestions welcome.  
> >   
 
<snip> 
 
> > Cheers  
> > Wayne 
> > 
> > 
> >    
> Hi Wayne, 
>    
> we may be able to help each other here. I have an LG working with  
> "three" (you've probably seen my article in the voice newsletter from a    
few 
> years back) - and yes since I've moved I also have to bear low speed  
> and roaming charges if I use this. I have just got a Next-G Samsung  
> SGH-A411 which I'm having a couple of issues with handshaking to 
> Next-G. 
>    
> You say you have your A501 working with Next-G - can you send me the  
> config string details please ? 
>    
> On the Sony - can you cut and paste the (trace on) messages from Injoy  
> (in fact if you haven't already done so compare what you have set  
> against what are in the screenshots in my article) - you might want to  send 
> all this info direct rather than on-list. 
>    
> In case you don't have it - here's the reference to my article: 
>    
> http://www.os2voice dot org/VNL/past_issues/VNL0606H/feature_1.html 
>    
>    
> Cheers/2 Ed. ---------------------------------------------------------------------------------- To 
 
Hi Ed 
 
I will send the Sony trace privately.  Connecting the Samsung (ME) we can   
do via this list so that others can benefit. 
 
Yes I used your excellent article as a basis & I had lots of teething troubles   
but the final settings were vastly different & now NextG is rock solid. 
1st thing to do is see if any CIDs are already set in the ME.  My Samsung   
had none set, the Sony had 2 CIDs set.  To see what is set, use a terminal   
program (eg. Zoc) & enter AT+CGDCONT? & let me know what the output is. 
Here is a copy from mine:- 
at+cgdcont? 
 
+CGDCONT: 1,"IP","telstra.internet","",0,0 
+CGDCONT: 2,"IP","3netaccess","",0,0 
 
OK 
 
I put CID2 in whilst experimenting & I can change it but not delete it. 
 
CAVEAT:-  Entering indiscriminate AT commands can do nasty things. 
It is quite safe if it ends in ? or =?.  This just queries a setting or a range of   
settings. 
 
Cheers 
Wayne


----------------------------------------------------------------------------------
 

**= Email   4 ==========================**

Date:  Fri, 31 Oct 2008 13:44:51 +1100
From:  Peter Moylan <peter at pmoylan dot org>
Subject:  Re:  Connecting a Sony W910i to the internet

On 31/10/08 08:09, Wayne wrote:
>  ** Reply to note from Peter Moylan <peter at pmoylan dot org> Thu, 30 Oct
>  2008 22:48:53 +1100
>
>  On 30/10/08 22:18, Wayne wrote:
>
> >> As a test, I tried connecting under windoze using Injoy v3 (comes
> >> with 2 NDIS drivers), success if drivers are installed, failed
> >> if not.
>
> > The fact that the extra NDIS drivers are required in Windows is
> > very suggestive. As I recall it, NDIS files are plain text files
> > that OS/2 also uses. Thus, you might have some luck in installing
> > those NDIS files into OS/2.
>
>  I found the 2 drivers but they are binary. How would I attempt to
>  install them? My test was done using XP.

Sorry for misleading you. It was my faulty memory. It's the NIF file 
that's plain text, not the NDIS file. However, it looks to me as if the 
NDIS file is simply a file of parameter settings, not an executable 
file; if you look at it with a plain text editor you get something 
that's almost readable, like a word processor file.

The next bit is ancient memory talking to me, and can't entirely be 
trusted. However, I seem to recall a bit of folklore about ethernet 
adapters that basically said "if your adapter doesn't have OS/2 support, 
don't worry, just install the generic NDIS support that most 
manufacturers supply". (Similarly, most graphics cards are 
VESA-compatible, which means that if you don't have a card-specific 
driver then a generic VESA driver will still work, albeit without access 
to any special "accelerator" features that the card might have.) This 
suggests to me that OS/2 already includes a generic NDIS driver, which 
requires only some configuration files that specify parameters that the 
NDIS driver uses to know how to the specific hardware.

In case it's any help, I'm reproducing below the installation 
instructions for a D-Link adapter that I have. They are practically 
identical to the installation instructions for every other ethernet 
adaptor I've seen. The only device-specific part is where you have to 
supply a path to the device-specific files. At that point, if the files 
are usable by the OS/2 software then it will let you move to the next 
step of the installation, and all will be OK. If they're not usable, the 
MPTS installer will say it can't find the files it needs. In that case 
you're screwed, of course.

Install the NDIS driver for IBM LAN SERVER 4.0
??????????????????????????????????????????????

 In the OS/2 Desktop group, double-click on the MPTS icon.

 Click on the <Configure> button.

 Select the "LAN adapters and protocols" option.

 Click on the <Configure> button.

 Select the "Other adapters ..." option.

 Insert the driver diskette in Drive A or B and type the driver path:

A:\<PATH>\ Where PATH is the driver directory.

or C:\<PATH>\ (if install program specify)

 Click on the <OK> button.

 Select "D-Link PCI Ethernet Adapter", and then click on the Add
button.

 Select "IBM OS/2 NETBIOS", and then click on the Add button.

 Select "IBM IEEE 802.2", and then click on the Add button.

 Click OK.

 Click Close.

 Click Exit.

 Reboot your system.



-- 
Peter Moylan peter at pmoylan dot org
http://www.pmoylan dot org

----------------------------------------------------------------------------------
 

**= Email   5 ==========================**

Date:  Fri, 31 Oct 2008 13:53:54 +1100
From:  Peter Moylan <peter at pmoylan dot org>
Subject:  Re:  Connecting a Sony W910i to the internet

P.S. I'll be off the air for the next little while. I've just taken 
delivery of a refurbished IBM Thinkcentre M50. (No monitor or keyboard, 
and the case is a little scratched, but I think it'll be worth the $300 
it cost me. The M50 got good reviews on the Russian eCS website.) The 
next step is to try to replace Windows with eCS. If that works, the 
machine I'm using to send this message will be retired from the desktop 
and put to work as a pure server.

But from past experience I know that it takes days to configure a new 
computer with the desired applications, to migrate things like mail and 
bookmarks, etc.

Actually, I still haven't even gotten as far as finding out whether the 
old computer will boot without a keyboard attached. Those old jokes 
about "No keyboard. Press any key to continue" weren't joking. It really 
happens. I'm just hoping that there's a BIOS setting to suppress the 
search for a keyboard.

-- 
Peter Moylan                          peter at pmoylan dot org
                                      http://www.pmoylan dot org

----------------------------------------------------------------------------------
 

**= Email   6 ==========================**

Date:  Fri, 31 Oct 2008 13:53:35 +0930
From:  Wayne <datablitz at optusnet dot com dot au>
Subject:  Re:  Connecting a Sony W910i to the internet

** Reply to note from Peter Moylan <peter at pmoylan dot org> Fri, 31 Oct 2008   
13:44:51 +1100 
>    
> > 
> >  I found the 2 drivers but they are binary. How would I attempt to 
> >  install them? My test was done using XP. 
>    
> Sorry for misleading you. It was my faulty memory. It's the NIF file  that's 
> plain text, not the NDIS file. However, it looks to me as if the  NDIS file is 
> simply a file of parameter settings, not an executable  file; if you look at it 
> with a plain text editor you get something  that's almost readable, like a 
> word processor file. 
>    
> The next bit is ancient memory talking to me, and can't entirely be  
> trusted. However, I seem to recall a bit of folklore about ethernet  adapters 
> that basically said "if your adapter doesn't have OS/2 support,  don't 
> worry, just install the generic NDIS support that most  manufacturers 
> supply". (Similarly, most graphics cards are  VESA-compatible, which 
> means that if you don't have a card-specific  driver then a generic VESA 
> driver will still work, albeit without access  to any special "accelerator" 
> features that the card might have.) This  suggests to me that OS/2 already 
> includes a generic NDIS driver, which  requires only some configuration 
> files that specify parameters that the  NDIS driver uses to know how to the 
> specific hardware. 
>    
> --  Peter Moylan peter at pmoylan dot org http://www.pmoylan dot org 
>    
 
OS2's .nif & .os2 are roughly the equivilant to windoze .inf & .sys files.    
However, a .nif has different & more info in it.  To translate a .inf to .nif is way   
beyond me & probably wouldn't be covered by Genmac either.  Thanks for   
your help. 
 
I will be away from a pc for the rest of the day. 
 
Cheers 
Wayne


----------------------------------------------------------------------------------
 

