Yes, I have tested it on 2 486s, an IBM ThinkPad 355c and a Toshiba
Satellite T2100CS, without problems.  Can you tell us (a lot) more about
the system on which it is now failing, and how it fails, at what point it
fails, and what (if any) messages it fails with?  It is probably a driver
change between 2.0.36 and 2.0.37, (2.0.38 is very close to 2.0.37), so
details of your scsi and network devices will help...  -Tom

> Anybody able to get this running on a 486 system?



Reply via email to