One of my users has 3 AMD6 350 machines running on a Windows 98 peer to peer network. The machines are behaving erratically. Periodically a message will display 'Device X not found on Network.' with options to abort retry or fail. The machine would then bail out to DOS on the network drive that it just said did not exist. All the machines would then have to be rebooted to get the program to work on any of them. What I know: the wiring is good, the hub is good, the cards are good and our software is running on many many similiar network systems without this problem. In non windows situations we set the config sys of each machine with himem.sys and emm386 noems. In win95 etc we dont set any devices at all in config sys and run the program thru PIF files which basically set memory to automatic. When I arrived on site the config sys of each system had himem loaded and the mem command at the DOS prompt showed that there was EMS memory. Typically this is bad so I initially remarked out the himem sys command thinking I had solved the problem. Several hours later the problem resurfaced. I then put himem back in and added the emm386 noems. Now the machines became truly flacky. Garbage began to be written into the files. The work stations would sometimes not go into the program at all. Unpacking zip files renamed the files with integers as the first letter of the file name. I them restored the config sys file to its original settings and went home scratching my head. Question: Are there any settings in the BIOS that could be causing this behavior?? Help!