Hi again,

 

I’ve having problems with the Boot CD on some hardware.  So far I’ve only be able to get it to work on one piece of hardware which is a Compaq Deskpro EN (1Ghz) although it didn’t work at first an I think I changed something in the bios and it started working, but I forgot what I changed.

 

 

I’m also trying it out with on an Gateway E1600 using the e100b driver and I get this error message and it just stops.

 

C: HD1, Pri [ 1], CHS=     0-1-1, start=      0 MB, size 2000 MB

FreeDOS HIHEM64 3.10 [Apr 22 2004] (c) 1995, Till Gerken 2001-2004 tom ehlert

Himem - Always On A20 method used

EMM386 1.11[April 25 2004] (c) ehlert 2001-2004 c't/H. Albrecth 1990

 

 

Illegal Instruction occured

CS=0000 IP=019E SS=00CF SP=0ED6 DS=0000 ES=00CF

EAX=00FC00D5 EBX=000000CF ECX=0000037B EDX=00000070

ESI=00000313 EDI=-00000574 EBP=00000874

Opcodes @CS:IP 63 03 F3 EE 00 F0 F3 EE

Aborting program

 

On a SE440BX-2 (450Mhz) board (a little bit of an older board, but it was popular chip set (with manufactures not end users) when it came out.

w/ the 3com 3c905c driver (el90x)

 

When I boot to that one I the network card just won’t bind and I get this error message.

 

Microsoft DOS TCP/IP NEMM Driver 1.0
The command completed successfully
MS-DOS LAN Manager v2.1 Netbind
Error: 36 Unable to bind. Hardware failure.
NET0125: NETBIND must be executed before TCP/IP TSR module is loaded.
        Unloadable TCP 1.0 not loaded.
NET0116: TCP access failure by Tiny RFC.
   Tiny RFC 1.0 not loaded.
Press any key to continue.

 

 

I get the same error message on an A-bit KG-7 Raid board with the 3c905c nic.

 

Ok… so that drove me crazy, but then I read this….

 

"Yeager, Elizabeth D" <[EMAIL PROTECTED]> writes:
 
 > When my client starts to boot FreeDos is just freaks out instead.
 > 
 > It gets as far as:
 > 
 > Loading Boot Sector... Booting...
 > then it spits out the version, and copyright info for FreeDos
 > after that it freaks. The messsages say:
 > 
 > Illegal instruction occured, then it prints out the contents of
 > different registers. 
 > It then does this ad nauseam.
 
 I made the mistake of switching to FreeDOS EMM386, which is not quite
 ready for prime time.  I reverted to UMBPCI for the next release.
 
 In config.sys, change these lines:
 
   ;; UMB provider
   ;DEVICE=umbpci.sys
   DEVICE=emm386.exe NOEMS
 
 ...to read:
 
   ;; UMB provider
   DEVICE=umbpci.sys
   ;DEVICE=emm386.exe NOEMS
 
 (That is, comment out the "emm386.exe" line and uncomment the
 "umbpci.sys" line.)
 
 That should help.  If not, please let me know.
 
-                   Pat

 

Alright!  Cool… this might be my answer. 

 

So, I tried this out (by just editing the config.sys and re-injecting it back in with WinImage) and it seems to work much better.

 

It works on Compaq Deskpro, Gateway E1600, SE-440BX, and abit KG7-RAID…. To a point.

 

L

 

They all boot up and it the umbpci.sys seems to recognize this hardware much better because the network cards all bind and I can connect (it maps a drive and the install starts) 

 

So, I tried it with a custom unattend.txt in the site folder and they run through (they seem to copy over the install files to the hard disk) until they get to certain point and they all just stop and say that it’s missing the CD and can’t continue.   Ok, ok… so maybe I messed up the unattend.txt some how…

 

So, I took my custom one out and just let it get built by the lovely perl scripts that I don’t understand have them make the unattend.txt for me.

 

The same thing happens with these except they stop at about the same point and ask for ftdisk.sys…  Hmm… I look in the folder and ftdisk.sy_ is there (on the Z: drive)

 

Ok, ok… so maybe I messed something up somewhere… So, I took another machine and downloaded everything from scratch, and recopied over the OS files from CD’s and tried it out again….

 

Same result.

 

Ok… well I’ll try out the Linux boot CD this time.  I got a little mixed up and for some reason thought that bookdisk.iso was the linuxboot.iso disk instead of the linux boot for the purposes of emulated a dos book  disk / A: drive… so. basically a dos boot disk.

 

Ok…. So I tried out Linux boot disk and that one works great.  I can switch between consoles with the Alt-F2… duh.. Why didn’t I realize this before…?

 

Anyway… the Linuxboot CD works well so for on two pieces of hardware. (The Compaq Deskpro en and the SE440BX-2 board)  Now… I’m trying it on an Abit KG7-Raid and it maps a drive and all that and then it dies at the end and says that it can’t find my hard drive on the Raid controller.  I looked like linux was identifying it, but it fails.  :’’’(

 

Any tips on troubleshooting this? 

 

~TIA

 

~DF

 

 

 

 

 

Reply via email to