🚀 go-pugleaf

Below are four messages posted which share some common problems, 
and ones I am having on a Windows 95 to Win 95 and Win 98 peer 
to peer.

The problem seems to be unrelated to whether it is Win95 or Win98.

Files and directories appear fine, but copy an exe or self extracting
archive across form machine to machine and they change their CRC and
become corrupt. Not only that, but the file dates get swicthed.

Cards are NE2000 or NE1000 compatible, cable in thin ethernet BNC
nodes are 50ohm terminated. Netbui and MS client and file & printer 
sharing :

Can anyone  advise?
                              o o o

From: jforsma@unix1.sncc.lsu.edu (Johan Forsman)
Newsgroups: comp.os.ms-windows.networking.win95
Subject: Strange behavior and corrupted transfers in W95 P2P
Date: Wed, 29 Apr 1998 14:31:06 GMT
Organization: Louisiana State University

Hello All:

I have wrestled with this for some time now, and many hours of
perusing Usenet and Web has netted me new knowledge but no solutions.

The problem is that transferring files between my laptop and desktop
at home (in a 2-computer network) is unreliable at best. The symptoms
are as follows:
 * Slow transfers (well, not as fast as at the university)
 * Sudden pauses of several seconds during transfers
 * Unpredictable corruption of files, especially larger executables
when copying from one computer to the other.

The laptop has a Linksys Combo card (10bT/10b2).
The desktop has a 3com509 card (10b2/AUI).
The cable is a RG62 with 50ohm resistors, one grounded.
I just recently bought the grounded terminator after being informed at
Johannes Helmig's web site, but the behavior of the network is the
same as with a non-grounded terminator.
The RG62 cable is a replacement for a bad generic coax cable, but
again the network behaves the same.

Both computers are running W95B, and I have tried any number of
combinations of protocols and settings with the same result.
File and Printer sharing is bound with NetBEUI.
TCPIP seemed to work better, but that configuration made it impossible
to telnet with my Dialup connection. I think also there were some
issues with having the 'real' IP# on my laptop (necessary for daily
work at the university) and the 'fake' IP# on my desktop.
IPX gave the same result as NetBEUI.
The laptop connects beautifully to any workgroup I want at the
University, using either NetBEUI (default) or TCPIP.

I have played with the Browse Master settings to no avail.

Any suggestions are more than welcome.

Thank you.

-----------------------
Johan Forsman
Graduate Student
Department of Geology and Geophysics
Louisiana State University
Baton Rouge, LA  70803
Telephone: (504) 388-8224
Telefax: (504) 388-2302
E-Mail: jforsma@unix1.sncc.lsu.edu

From: smcdnld@netcomuk.co.uk (Stephen McDonald)
Newsgroups: comp.os.ms-windows.networking.misc,comp.os.ms-windows.networking.win95,comp.os.ms-windows.networking.windows
Subject: HELP! Error in zips file & bitmaps transfered over Peer2Peer
Date: Wed, 13 May 1998 18:34:53 GMT

I have a peer 2 peer network setup between three pc's. 

I've grounded one end of the network. 
I'm using 50ohm terminators. 
All machines running windows 95

It works fine in most except when I copy a zip file from one machine
to the other. They always come over corrupt. The same with bitmaps

Transferring Word document or spreadsheets seems fine.

Can anyone help!

TIA
Stephen McDonald


From: "David \"Zarquon\"" <pck@hotkey.net.au>
Newsgroups: comp.os.ms-windows.networking.win95
Subject: Data Corruption during network XFer
Date: Wed, 27 May 1998 17:58:33 +1000

I have a peer-to-peer network with 3 computers connected through coax.
Two are desktops, one is a laptop. The two desktops have Windows 98 and
Windows 95 OSR2, while the laptop has Windows 95 normal. The two
desktops are connected on either ends of the network, with the laptop in
the middle. Protocals used are IPX/SPX and TCP/IP.
  Data transfer between the two desktops have no problems. However, data
is ALWAYS corrupted when transferring between either of the desktops and
the laptop. I have already installed the patch provided by Microsoft to
fix the loophole with MS-Client caching, without changes. Could somebody
please help me fix this?

From: Ryan Honeyman <honeyman@infi.net>
Newsgroups: comp.os.ms-windows.networking.misc,comp.os.ms-windows.networking.win95,comp.os.ms-windows.networking.windows
Subject: Win98/Win95 Networking.
Date: Tue, 23 Jun 1998 10:55:34 -0400

Problem:  When attempting to transfer files across the local BNC
          network from a Win98 to a Win95b computer, several compressed
          zip files are corrupted and have CRC failures.  It is random
          which files are affected each time, and this is true of other
          compressed and non-compressed files.

Background:  Didn't have any problems with Win95 to Win95, until the one
             computer on the network was upgraded to Win98.  Microsoft
             NET DIAG from the dos prompt doesn't show any errors, but
             when a NET VIEW is run the Win98 computer shows up as
             two network resources.  So you would see \\HOSTNAME and
             then a garbled \\%^&#& (some high ascii chars also) 
             as well; both have the same Remark field.

Info:  Both computers have generic ne2000 ethernet combo cards which 
       have worked up to this point.  Both systems are running IPx/SPx
       and NetBIOS protocols, which seem to test fine.  Only when
       transfering files from one to the other do problems arise in the
       integrity of the data transfer.  These are the only two computers
       on the 10base2 network and can see each fine via network       
browsing.

Any suggestions?

-- 
David Longley

Longley Consulting                                                  London, UK
Behaviour Assessment & Profiling Technology,
Research, Data Analysis and Training Services,
Small IT Systems                                http://www.longley.demon.co.uk

In demon.tech.pc, David Longley wrote:

>I've noticed several times when I have peer networked under  W95, 
>selecting MS NETBUI and client etc, that under some condition, my 
>files end up being corrupted when copied across from one  machine 

I'm not sure, but I think it may be because Microsoft networking is "crap".

-- 
Bob Cousins, Software Engineer.
Home page at http://www.lintilla.demon.co.uk/

In article <35ea3a1a.25289604@news.demon.co.uk>
           bob@lintilla.demon.co.uk "Bob Cousins" writes:

> >I'm sure those who can't transfer data reliably are using crap
> >hardware, probably within the pc rather than the network. Or
> >incapable of configuring whatever...
> 
> Standard excuse #1! The *test* of good network software is faulty hardware.

I did say above 'crap h/w.......within the pc'. I totally agree that
decent network s/w should cope with poor external network h/w.

Ernest
-- 
ernest     at Noel Systems, near Kingston-upon-Thames (UK)
           (if replying by email, use postmaster)

In article <35e59f86.9989894@news.demon.co.uk>
           bob@lintilla.demon.co.uk "Bob Cousins" writes:

> I'm not sure, but I think it may be because Microsoft networking is "crap".

Oh come on Bob. The world as we know it would have come to a
complete stand still if Billy's networks didn't transfer data
packets (and files) reliably, day in day out.

I'm sure those who can't transfer data reliably are using crap
hardware, probably within the pc rather than the network. Or
incapable of configuring whatever...

Ernest
-- 
ernest     at Noel Systems, near Kingston-upon-Thames (UK)
           (if replying by email, use postmaster)

In article <903641590snz@longley.demon.co.uk>
           David@longley.demon.co.uk "David Longley" writes:

There have, alas, been a series of singularly unhelpful posts  in 
the  wake of the problem outlined below. I'm reposting it in  the 
beleif  that this must have been encountered before  and  someone 
must know of some solution.

And preferably - no more of the unhelpful comments.

> Below are four messages posted which share some common problems, 
> and ones I am having on a Windows 95 to Win 95 and Win 98 peer 
> to peer.
> 
> The problem seems to be unrelated to whether it is Win95 or Win98.
> 
> Files and directories appear fine, but copy an exe or self extracting
> archive across form machine to machine and they change their CRC and
> become corrupt. Not only that, but the file dates get swicthed.
> 
> Cards are NE2000 or NE1000 compatible, cable in thin ethernet BNC
> nodes are 50ohm terminated. Netbui and MS client and file & printer 
> sharing :
> 
> Can anyone  advise?
>                               o o o
> 
> From: jforsma@unix1.sncc.lsu.edu (Johan Forsman)
> Newsgroups: comp.os.ms-windows.networking.win95
> Subject: Strange behavior and corrupted transfers in W95 P2P
> Date: Wed, 29 Apr 1998 14:31:06 GMT
> Organization: Louisiana State University
> 
> Hello All:
> 
> I have wrestled with this for some time now, and many hours of
> perusing Usenet and Web has netted me new knowledge but no solutions.
> 
> The problem is that transferring files between my laptop and desktop
> at home (in a 2-computer network) is unreliable at best. The symptoms
> are as follows:
>  * Slow transfers (well, not as fast as at the university)
>  * Sudden pauses of several seconds during transfers
>  * Unpredictable corruption of files, especially larger executables
> when copying from one computer to the other.
> 
> The laptop has a Linksys Combo card (10bT/10b2).
> The desktop has a 3com509 card (10b2/AUI).
> The cable is a RG62 with 50ohm resistors, one grounded.
> I just recently bought the grounded terminator after being informed at
> Johannes Helmig's web site, but the behavior of the network is the
> same as with a non-grounded terminator.
> The RG62 cable is a replacement for a bad generic coax cable, but
> again the network behaves the same.
> 
> Both computers are running W95B, and I have tried any number of
> combinations of protocols and settings with the same result.
> File and Printer sharing is bound with NetBEUI.
> TCPIP seemed to work better, but that configuration made it impossible
> to telnet with my Dialup connection. I think also there were some
> issues with having the 'real' IP# on my laptop (necessary for daily
> work at the university) and the 'fake' IP# on my desktop.
> IPX gave the same result as NetBEUI.
> The laptop connects beautifully to any workgroup I want at the
> University, using either NetBEUI (default) or TCPIP.
> 
> I have played with the Browse Master settings to no avail.
> 
> Any suggestions are more than welcome.
> 
> Thank you.
> 
> -----------------------
> Johan Forsman
> Graduate Student
> Department of Geology and Geophysics
> Louisiana State University
> Baton Rouge, LA  70803
> Telephone: (504) 388-8224
> Telefax: (504) 388-2302
> E-Mail: jforsma@unix1.sncc.lsu.edu
> 
> From: smcdnld@netcomuk.co.uk (Stephen McDonald)
> Newsgroups: comp.os.ms-windows.networking.misc,com
> p.os.ms-windows.networking.win95,comp.os.ms-windows.networking.windows
> Subject: HELP! Error in zips file & bitmaps transfered over Peer2Peer
> Date: Wed, 13 May 1998 18:34:53 GMT
> 
> I have a peer 2 peer network setup between three pc's. 
> 
> I've grounded one end of the network. 
> I'm using 50ohm terminators. 
> All machines running windows 95
> 
> It works fine in most except when I copy a zip file from one machine
> to the other. They always come over corrupt. The same with bitmaps
> 
> Transferring Word document or spreadsheets seems fine.
> 
> Can anyone help!
> 
> TIA
> Stephen McDonald
> 
> 
> From: "David \"Zarquon\"" <pck@hotkey.net.au>
> Newsgroups: comp.os.ms-windows.networking.win95
> Subject: Data Corruption during network XFer
> Date: Wed, 27 May 1998 17:58:33 +1000
> 
> I have a peer-to-peer network with 3 computers connected through coax.
> Two are desktops, one is a laptop. The two desktops have Windows 98 and
> Windows 95 OSR2, while the laptop has Windows 95 normal. The two
> desktops are connected on either ends of the network, with the laptop in
> the middle. Protocals used are IPX/SPX and TCP/IP.
>   Data transfer between the two desktops have no problems. However, data
> is ALWAYS corrupted when transferring between either of the desktops and
> the laptop. I have already installed the patch provided by Microsoft to
> fix the loophole with MS-Client caching, without changes. Could somebody
> please help me fix this?
> 
> From: Ryan Honeyman <honeyman@infi.net>
> Newsgroups: comp.os.ms-windows.networking.misc,com
> p.os.ms-windows.networking.win95,comp.os.ms-windows.networking.windows
> Subject: Win98/Win95 Networking.
> Date: Tue, 23 Jun 1998 10:55:34 -0400
> 
> Problem:  When attempting to transfer files across the local BNC
>           network from a Win98 to a Win95b computer, several compressed
>           zip files are corrupted and have CRC failures.  It is random
>           which files are affected each time, and this is true of other
>           compressed and non-compressed files.
> 
> Background:  Didn't have any problems with Win95 to Win95, until the one
>              computer on the network was upgraded to Win98.  Microsoft
>              NET DIAG from the dos prompt doesn't show any errors, but
>              when a NET VIEW is run the Win98 computer shows up as
>              two network resources.  So you would see \\HOSTNAME and
>              then a garbled \\%^&#& (some high ascii chars also) 
>              as well; both have the same Remark field.
> 
> Info:  Both computers have generic ne2000 ethernet combo cards which 
>        have worked up to this point.  Both systems are running IPx/SPx
>        and NetBIOS protocols, which seem to test fine.  Only when
>        transfering files from one to the other do problems arise in the
>        integrity of the data transfer.  These are the only two computers
>        on the 10base2 network and can see each fine via network       
> browsing.
> 
> Any suggestions?
> 

-- 
David Longley (check end reply line #)

Longley Consulting                                                  London, UK
Behaviour Assessment & Profiling Technology,
Research, Data Analysis and Training Services,
Small IT Systems                                http://www.longley.demon.co.uk

In article <903669956snz@ex-change.demon.co.uk>
           Douggie@ex-change.demon.co.uk "Douggie Green" writes:

> FFS, all you had to say was "this seems to to be a common problem",

ROFL, trying to tell DL anything sensible AND then expecting a
result!

Ernest
-- 
ernest     at Noel Systems, near Kingston-upon-Thames (UK)
           (if replying by email, use postmaster)

In article <903631590snz@longley.demon.co.uk>, David Longley
<David@longley.demon.co.uk> writes
>I've noticed several times when I have peer networked under  W95, 
>selecting MS NETBUI and client etc, that under some condition, my 
>files end up being corrupted when copied across from one  machine 
>to the other. There are three nodes on the network. Cards are all 
>working  OK,  directories  are  all listing  OK,  but  when  self 
>extracing archives are copied across and I do a CRC on the  local 
>vs remote file, the CRCs do not match, and attempting to  extract 
>produces corrupt file messages.

David, it won't work with wet string.

>N2000 and NE1000 cards
           ^^^^^^
You cheap slut!  It's only 12 quid for a PnP network card.

TB                           Team TSF(UK)

In article <903641590snz@longley.demon.co.uk>
           David@longley.demon.co.uk "David Longley" writes:

> Below are four messages posted which share some common problems, 
> and ones I am having on a Windows 95 to Win 95 and Win 98 peer 
> to peer.
> 
FFS, all you had to say was "this seems to to be a common problem",
and maybe post the article ID's.

[slash]
[plonk]

Douggie

Details:  The NE2000 compatible card in the P166 is a D-LINK  DE-
200+ which allows IRQ 2-15. If anyone has the jumper settings for 
IO and MEM that would be helpful.
-- 
David Longley (check end reply line #)

Longley Consulting                                                  London, UK
Behaviour Assessment & Profiling Technology,
Research, Data Analysis and Training Services,
Small IT Systems                                http://www.longley.demon.co.uk

Well,  thanks  to  several  bits of advice, I  think  it  is  now 
identified as a NIC problem in the P166. The card is a D-LINK DE-
200+  ISA non PnP card. According to the D-LINK UK  website,  the 
DE-200+ is not 100% NE2000 driver compatible, in that the  latest 
NE2000 drivers x1Ch to reset, older drivers using x1Ch-x1Fh.  The 
DE-200+ explicitly uses x1Fh for this making it incompatible with 
newer  NE2000 drivers. They recommend using DLINK drivers  -  but 
those available seem to just lock my system.

I've  decided  to disable my soundcard on IRQ 5 and  use  another 
standard Ne2000 card with IRQ 5. That works, but I really need  a 
card which can use IRQ 12 without these problems (PCI or ISA).

-- 
David Longley (check end reply line #)

Longley Consulting                                                  London, UK
Behaviour Assessment & Profiling Technology,
Research, Data Analysis and Training Services,
Small IT Systems                                http://www.longley.demon.co.uk

In article <903725726snz@noelsys.demon.co.uk>
           ernest@noelsys.demon.co.uk "Ernest" writes:

> In article <903669956snz@ex-change.demon.co.uk>
>            Douggie@ex-change.demon.co.uk "Douggie Green" writes:
> 
> > FFS, all you had to say was "this seems to to be a common problem",
> 
> ROFL, trying to tell DL anything sensible AND then expecting a
> result!
> 
Yeah, I know. He's totally clueless :(

Douggie

Mikey wrote in message <6rmppa$vsk$1@news.iinet.net.au>...
>i had the same problems with crc errors in zips and compressed
files..across
>my LAN
>my solution,,i swapped both my pci network cards for isa ones which can
>manually set irq..and i set both to hav irq 5 on both machines..
>now no crc errors at all..
>btw..i only installed TCP/IP ...No IPX and NO netbui!!
>i can still share files and printers and have had no probs with wingate for
>sharing 1 DUN I-Net accnt.
>Both machines run win98 and one is PII,the other old P-166
>
>interestingly, i talked to a tech in a local shop and he said with some
>motherboards, pci network cards have a hard time gettin configured..
>he was the one who advised the cheapie ISA cards and they worked first
>time(and evry time),unlike the pci versions...

Ditto!!! had the peachy PCI card Plug and Pray...didnt' work for S****
conflicts galore!Degraded to a ISA with jumpers..ah! all is
well...Suggestion?? make sure those Plug and Pray cards are located as FAR
from the mother board power connectors as possible. and those ISA as CLOSE
to the mother board power connectors as possible....has something to do with
the Bus enumerator. Seems to load up those cards with less
problemos...>mikey
>
>

On Fri, 21 Aug 98 20:06:49 GMT, David Longley <David@longley.demon.co.uk> wrote:

>And preferably - no more of the unhelpful comments.

Ok I'll try. 

<snip problem>

> Cards are NE2000 or NE1000 compatible, cable in thin ethernet BNC
> nodes are 50ohm terminated. Netbui and MS client and file & printer 
> sharing :
 
> Can anyone  advise?

I had the same problem or at least a very simalar one. It took a little
while to track down, but it was definatly fixable. 

So I assume you will be able to fix you problem. Keep trying you will get
there in the end. 

HTH. 

-- 
   AxxE@drk1.demon.co.uk    ICQ:2526788        http://www.drk1.demon.co.uk
-----------------------Interested in fighting spam?---------------------------
AGSF mirror http://www.drk1.demon.co.uk/ags-f/  also see http://www.sputum.com

In demon.tech.pc, David Longley wrote:

>> Any suggestions?

Yeah, reposting *in full* what you just posted is a complete waste of resources.
I'll expect you'll get a lot of helpful replies now.

-- 
Bob Cousins, Software Engineer.
Home page at http://www.lintilla.demon.co.uk/

In demon.tech.pc, Ernest wrote:

>In article <35e59f86.9989894@news.demon.co.uk>
>           bob@lintilla.demon.co.uk "Bob Cousins" writes:
>
>> I'm not sure, but I think it may be because Microsoft networking is "crap".
>
>Oh come on Bob. The world as we know it would have come to a
>complete stand still if Billy's networks didn't transfer data
>packets (and files) reliably, day in day out.

The Internet uses Microsoft networking?! 

Seriously, my world came to a standstill and started to go backwards when a
vital network database (also Microsoft) got corrupted. After hanging on the
phone for a few hours, the best answer we got from MicroSoft was, we don't know
why, you'll have to recreate the database. Well we did, but the next network
error screwed it again.

Most sites I go to have frequent problems with Microsoft based networks. MS gets
used not because its the best or most reliable, its because its cheap.

Plus when you add up all the other weaknesses in protocols, bugs in
implementation, and security holes, I wouldn't consider using MS stuff for
anything important. Novell seem to know their stuff, and TCP/IP has a very fine
pedigree.

>I'm sure those who can't transfer data reliably are using crap
>hardware, probably within the pc rather than the network. Or
>incapable of configuring whatever...

Standard excuse #1! The *test* of good network software is faulty hardware.
-- 
Bob Cousins, Software Engineer.
Home page at http://www.lintilla.demon.co.uk/

Bob Cousins wrote:
> 
> In demon.tech.pc, Ernest wrote:
> 
<snip>
> >I'm sure those who can't transfer data reliably are using crap
> >hardware, probably within the pc rather than the network. Or
> >incapable of configuring whatever...
> 
> Standard excuse #1! The *test* of good network software is faulty hardware.
> --
> Bob Cousins, Software Engineer.
> Home page at http://www.lintilla.demon.co.uk/

Truer words have seldom been spoken.  If it can't recover, or at least
detect problems and degrade gracefully, it's just a toy.

Progress:

There are 4 nodes max on this net:

Thinkpad 755CX in DOCK II with Xircom PCMCIA BNC 
486-66DX2 - 1 with NE2000 compatible IRQ 5  IO 300
486-66DX2 - 2 with NE1000 compitible IRQ 5  IO 300
P166      -   with NE2000 compatible IRQ 12 IO 300

Terminated  with 50 ohm terminators. Files seem to transfer OK  if 
the P166 is taken off.

It  is  not  the  cabling (RG58 is  used  throughout).  I'll  try 
replacing  the NE2000 in the P166, but finding one which uses IRQ 
12 (all that's free) may be a problem.

Anyone have DOS config files for a 3COM 3C509 COMBO etherlink III?

W95 reports no problems on the p166 with the card or drivers.

-- 
David Longley (check end reply line #)

Longley Consulting                                                  London, UK
Behaviour Assessment & Profiling Technology,
Research, Data Analysis and Training Services,
Small IT Systems                                http://www.longley.demon.co.uk

In article <903816128snz@longley.demon.co.uk>, David Longley
<David@longley.demon.co.uk> writes

>I've  decided  to disable my soundcard on IRQ 5 and  use  another 
>standard Ne2000 card with IRQ 5. That works, but I really need  a 
>card which can use IRQ 12 without these problems (PCI or ISA).

What's wrong with IRQ 2/9?

TB                           Team TSF(UK)

i had the same problems with crc errors in zips and compressed files..across
my LAN
my solution,,i swapped both my pci network cards for isa ones which can
manually set irq..and i set both to hav irq 5 on both machines..
now no crc errors at all..
btw..i only installed TCP/IP ...No IPX and NO netbui!!
i can still share files and printers and have had no probs with wingate for
sharing 1 DUN I-Net accnt.
Both machines run win98 and one is PII,the other old P-166

interestingly, i talked to a tech in a local shop and he said with some
motherboards, pci network cards have a hard time gettin configured..
he was the one who advised the cheapie ISA cards and they worked first
time(and evry time),unlike the pci versions...

mikey

It's  odd,  but  Windows  95 clearly indicates  that  a  card  is 
working  properly  with  no  conflicts even if  the  IO  and  RAM 
addresses  are  not entered as they are on  the  physical  jumper 
configuration.  Some  of  the  W95 drivers  don't  give  you  the 
opportunity to alter the IRQ or RAM address.

I'll see what D-LINK have to say about the DE 200+ under W95, and 
post  a follow up. There *are* drivers for what they call the  DE 
22x  family (which include the older DE200 and DE200+, but on  my 
system,  W95  just locks on the opening screen when I  try  using 
them.

-- 
David Longley (check end reply line #)

Longley Consulting                                                  London, UK
Behaviour Assessment & Profiling Technology,
Research, Data Analysis and Training Services,
Small IT Systems                                http://www.longley.demon.co.uk

In article <903725726snz@noelsys.demon.co.uk>
           ernest@noelsys.demon.co.uk "Ernest" writes:

> In article <903669956snz@ex-change.demon.co.uk>
>            Douggie@ex-change.demon.co.uk "Douggie Green" writes:
> 
> > FFS, all you had to say was "this seems to to be a common problem",
> 
> ROFL, trying to tell DL anything sensible AND then expecting a
> result!
> 
> Ernest
> -- 
> ernest     at Noel Systems, near Kingston-upon-Thames (UK)
>            (if replying by email, use postmaster)
> 

That assumes you have had something "sensible" to say.
-- 
David Longley (check end reply line #)

Longley Consulting                                                  London, UK
Behaviour Assessment & Profiling Technology,
Research, Data Analysis and Training Services,
Small IT Systems                                http://www.longley.demon.co.uk