Conference noted::etherworks

>>    Do we (and if not, when will we) have Windows 95 OSR2 drivers for our
>>    NICs.  A customer got a Gateway Laptop with OSR2 and it does not
>>    recognize the oemsetup.inf on the DEPCM driver disk.
>>    
>>    Michael
    
    OSR2 should be compatible to oemsetup.inf (and Win95 drivers). OSR2 is 
    a service release (only given to OEM's) for Win95 that basically includes 
    bug fixes and a new file system FAT32. I've seen sometimes when I've
    installed other products that Win95 has problems finding the file
    (oemsetup.inf) and on subsequent retries(e.g. starting all over) it 
    finds it. He may want to recheck this. Also just to make sure you might 
    want to try another installation diskette.
    
    FYI, there is information on OSR2 at:
    
    		http://www.microsoft.com/windows/pr/win95osr.htm
    
    There is information on PCMCIA enhancments however this is primarily
    support for the new Cardbus PCMCIA cards....
    
    -Pete

I have a problem with a DEPCM and Win95 OSR2, it was working fine 
before OSR2, now if get's recognised when I plug it in, and asks for 
the drivers, I insert the drivers v2.0 disketter (as I have a Rev A 
card) and it says "The selected location does not contain a driver 
for your device"

any ideas? I'm desperate to get this working having spent 4 hours 
yesterday trying combinations of the v4 and the v2 drivers.

Help!!

Greg

    Try updating the driver through Device Manager instead.
    
    Also make sure that you use resources that are available.
    
    Bernard

Fixed this, but don't understand why, perhaps someone can enlighten 
me.

In netlog, I noticed it thought the DEPCM was a 
DIGITAL-DEPCM-XX-84E6, which wasn't in the .inf descriptions for v2.0 
or v4.0 drivers.

I changed the v4.0 .inf to recognise the above card, and it installed 
the drivers!

Can anyone explain why? I thought I had a rev A card.

Greg

Can you elaborate on the changes you made to the INF file to get the DEPCM drivers to work on 
OSR2?  I have a different solution that appears to work:

I worked on a users HiNote VP575 a few weeks ago.  He has an Accton EN2216 ethernet card, 
which looks just like a DEPCM-BA card.  I then tried a DEPCM-BA card on an OSR2 system, 
setting the driver to the Accton EN2216 PCMCIA card, and it works just fine.  I don't know if 
there are any long term issues, or if we can use this in support of external customers 
though.

Regards,

Greg Sachs
[email protected]

Here's what I did, I'd love to know how/why it occured:

I looked in the netlog file in c:\, which looked like this:

NETDI: ClassInstall (0x6 on 0x3326:0x2924) on Digital EtherWORKS 
PCMCIA Turbo Adapter at Enum\PCMCIA\DIGITAL-DEPCM-XX-84E6\0
NETDI: Examining class Net
NETDI: Found Enum\PCMCIA\DIGITAL-DEPCM-XX-84E6\0 in registry
NETDI: NdiCreate(Digital EtherWORKS PCMCIA Turbo Adapter) OK
NETDI: Found Enum\PCMCIA\DIGITAL-DEPCM-XX-C293\0 in registry
NETDI: NdiCreate(Digital EtherWORKS PCMCIA Turbo Adapter) OK
NETDI: Found Enum\PCMCIA\XIRCOM-CREDITCARD_10BASE-T-64BA\0 in 
registry
NETDI: NdiCreate(Xircom CE-IIps CreditCard Ethernet Adapter (XPS 
Driver)) OK
NETDI: Found Enum\PCMCIA\XIRCOM-CREDITCARD_10BASE-T-5331\0 in 
registry
NETDI: NdiCreate(Xircom CE-IIps CreditCard Ethernet Adapter (XPS 
Driver)) OK
NETDI: Found Enum\Root\Net\0000 in registry

Then the 1st part of my depcm.inf is (only bit I changed was the 4 
letter code on the last line)

; DEPCM.INF
;
; Ethernet PCMCIA Adapter INF file for Windows 95
;

[version]
signature="$CHICAGO$"
Class=Net
provider=%V_MS%

[Manufacturer]
;%V_PCMCIA%=PCMCIA
%V_DEC%=DEC

[DEC]
%DEPCM.DeviceDesc%=DEPCM.ndi,PCMCIA\DIGITAL-DEPCM-XX-84e6

    There is a bug in the win95 setup file for depcm that shows up with
    osr2.  A new setup file is being tested and will be made available
    shortly.
    
    Regards,
    Janice