On Sat, 19 Feb 2005, Vintage Computer Festival wrote:
>
> I've got a DOS 6.22 machine with Microsoft Network Client installed so I
> can mount volumes on my XP machine. All works fairly well. The problem
> is when I try to copy lots of files to the XP machine. The DOS system
> invariably hangs and I have to reboot.
>
> At first I was using PUTR to copy the contents of dozens of disk images
> over to the mounted drive on the XP box. At various points (normally on
> very big files) it would crash and I'd have to reboot. I tried various
> things like disabling certain things getting loaded (DOSKEY), making stuff
> load low instead of high, etc. Nothing really helped. I was able to copy
> over all the files if I rebooted and tried the copy again. Where it would
> crash before it would now work fine and I could move on to the next image,
> and the next, etc. until another crash.
>
> Is this a known problem? I tried tweaking the network configuration
> (including arbitrarily reducing the packet size from 1498 to 1024) but I
> can't find anything that will stop the machine from crashing. This is
> very frustrating.
>
> One stupid thing about PUTR: it copies in ASCII mode as a default, instead
> of binary. This is stupid stupid stupid! In the PC world where
> everything is 8-bit based, why default to ASCII? I was all but done
> copying over all the disk images when I noticed that when PUTR first
> starts it tells you the copy mode defaults to ASCII. ARGH!! Stupid
> stupid stupid!!!
>
> --
>
> Sellam Ismail Vintage Computer Festival
> ------------------------------------------------------------------------------
> International Man of Intrigue and Danger http://www.vintage.org
>
> [ Old computing resources for business || Buy/Sell/Trade Vintage Computers ]
> [ and academia at www.VintageTech.com || at http://marketplace.vintage.org ]
>
Dont know about XP, (we have a few DOS clients on a Samba server) but I have
seen this problem with bad Ethernet card / and or drivers on the DOS side (the
National DP83815 packet driver is known bad this way). You may want to try
changing the Ethernet card/driver set to eliminate it as a possible cause.
Peter Wallace
Received on Sat Feb 19 2005 - 13:28:57 GMT