huff@kuhub.cc.ukans.edu (Steve Huff, University of Kansas, Lawrence) (12/21/90)
We have 10 PCs that do nothing but control LANs, printers, T1s and all kinds of other fun stuff. The problem is that these PS/2s will not boot w/out a monitor and keyboard attached. Is there a util available to get around this? How about a cheap hardware piece? We prefer purchasable software but I'm willing to evaluate shareware and public domain. Please e-mail or followup here. Thanks for your support. Steve ------------------------------------------------------------------------------- Steve Huff, student, University of Kansas HomeNet: 913 749 4720 Internet: HUFF@kuhub.cc.ukans.edu Bitnet: HUFF@Ukanvax.Bitnet Don't_hold_your_breath_net: P.O. Box 1225, Lawrence, KS 66044-8225 -------------------------------------------------------------------------------
archer@stlvm2.iinus1.ibm.com ("Gary D. Archer") (12/22/90)
>> huff@kuhub.cc.ukans.edu (Steve Huff, University of Kansas, Lawrence) writes: >> We have 10 PCs that do nothing but control LANs, printers, T1s and >> all kinds of other fun stuff. The problem is that these PS/2s will >> not boot w/out a monitor and keyboard attached. >> >> Is there a util available to get around this? How about a cheap >> hardware piece? We prefer purchasable software but I'm willing to >> evaluate shareware and public domain. >> This is very simple to do if you're willing to boot from a floppy (I don't think that it works with the HD). Consider the configuration disk.. this disk has to boot the system even if there is a problem with it (ie keyboard problem)... and the user couldn't press the F1 key.. If you examine the boot record of a standard bootable floopy, and then compare it with the configuration disk you will notice 1 difference right after the letters IBM. The configuration disk has the character Y and a regular disk has a blank (or null). You could use Norton to Edit regular boot disks, or use DISKCOPY and then erase everything off the new disk (the configuration disk's command.com is different), and copy over enough files to make them boot. AUTOEXEC.BAT You might want to check the boot record on the HD to see if it follows this pattern too. Gary