|  |     I, too, am having problems getting a DE203 to work on a VenturisFP
    system running Windows 95 with Service pack 1.  I copied and have used
    the EZWORKS V2.11 to configure the card with I/O port 1000, IRQ 10 and
    memory 000D8000.  I've triple-checked that I have the same values set
    in the Network section for the card, and they are the same.  Yet, when
    I boot the system, the sound card gives only a peep, instead of the
    2-second music piece I usually hear.  So, I'm assuming there is a
    conflict.  Yet, I removed the sound card, and the sound card presence
    in System Properties, and still I get an error message when I invoke
    Network Neighborhood.  Oddly, if I remove the DE203, and reboot,
    Networker Neighborhood is able to browse resources on the local
    machine.
    
    I took a look at the \windows\ndislog.txt; it exists, but is a blank
    file.
    
    What else can I check?
    
    Thanks!
    tl
 | 
|  | >>    I, too, am having problems getting a DE203 to work on a VenturisFP
>>    system running Windows 95 with Service pack 1.  I copied and have used
>>    the EZWORKS V2.11 to configure the card with I/O port 1000, IRQ 10 and
>>    memory 000D8000.  I've triple-checked that I have the same values set
>>    in the Network section for the card, and they are the same.  Yet, when
>>    I boot the system, the sound card gives only a peep, instead of the
>>    2-second music piece I usually hear.  So, I'm assuming there is a
>>    conflict.  Yet, I removed the sound card, and the sound card presence
>>    in System Properties, and still I get an error message when I invoke
>>    Network Neighborhood.  Oddly, if I remove the DE203, and reboot,
>>    Networker Neighborhood is able to browse resources on the local
>>    machine.
>>    
>>    I took a look at the \windows\ndislog.txt; it exists, but is a blank
>>    file.
    
    
    Under Control Panel click on System and select Device Manager. Click on
    Network Adapters and select the EtherWORKS 3 card and view its
    Properties. The Device Status should show:
    
    		    "This device is working properly"
    
    If not then you got a hardware conflict you need to resolve. However
    one gotcha with the Network Neighborhood that I found was that if you
    do not specify a valid Workgroup(under Identification found in the Network 
    Icon) and try to click on "Entire Network" you can get an error message.
    which makes it appear that there is a problem with your adapter setup.
    What is the error message you are getting? Is it when you first click on 
    "Network Neighborhood"? Or is it when your inside "Network Neighborhood" 
    and try to click on "Entire Network".
    
    -Pete
 | 
|  |     Pete
    
    Thanks for taking the time to respond.  I just tried, again, and
    everything worked just fine.  The only thing I did was to give up late
    last night, power everything off, and leave it off until this morning. 
    Very strange.
    
    Thanks again!
    tl
 |