FYI. The symptoms described in the exchange below seem to be resolved in the Unattended 2.5 release with the synch with FreeDOS fdisk 1.1.4 beta.
YEAH! Scott -----Original Message----- From: Jason Brady [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 18, 2003 12:53 PM To: Scott Card Cc: [EMAIL PROTECTED] Subject: Re: [Unattended] Cd boot error I've only been using 2.3b, haven't tried 2.4 yet, but I got this error message on an old dell Optiplex. Turns out that it didn't like how install.pl set the "use LBA" option. If I ran the partition commands manually, it worked, but when install.pl ran it, it returned that same error. I also added an fdisk.ini from the fdisk website, http://www.23cc.com/free-fdisk/, and if I commented out the part where it actually set the option in install.pl, it worked. Jason ----- Original Message ----- From: "Scott Card" <[EMAIL PROTECTED]> To: "Patrick J. LoPresti" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Friday, February 14, 2003 2:32 PM Subject: RE: [Unattended] Cd boot error Well, I've done a little testing but am just chasing my tail... > What happens if you run "fdisk /info /tech" by hand after the error? It throws the following error: "The "FLAG_SECTOR" value in the "fdisk.ini" file is out of range... Operation Terminated" > So try "fdisk /info /tech 2" and see what that does. Same error as above. In fact, fdisk won't run at all except for to print it's usage info. However, when I use a boot floppy all is well. Also, these errors are definitely new to 2.4, they didn't exist in 2.3. Scott -----Original Message----- From: Patrick J. LoPresti [mailto:[EMAIL PROTECTED] Sent: Thursday, February 13, 2003 10:52 AM To: Scott Card Cc: [EMAIL PROTECTED] Subject: Re: [Unattended] Cd boot error "Scott Card" <[EMAIL PROTECTED]> writes: > When I boot from the stock 2.4 CD to el90x driver. Just past OS > selection I get the following error: > > Fdisk /info /tech > a:\temp.txt failed, status 3 ... > > Any ideas? Does it print out the IP address and MAC address? If so, the problem is probably with the fdisk command itself (as opposed to writing the temp file). What happens if you run "fdisk /info /tech" by hand after the error? I think I have seen something similar, where fdisk considers the CD-ROM to be drive 1 (which is its default). So try "fdisk /info /tech 2" and see what that does. I do not have any good solution for this, other than to use a floppy or PXE boot instead. Hm. I suppose install.pl could "hunt" for the right drive by running fdisk repeatedly ("fdisk /info 1", "fdisk /info 2", and so on) until it did not get an error. But this is arguably a bug in FreeDOS fdisk; it should probably skip CD-ROM drives automatically. - Pat ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info ------------------------------------------------------- This SF.net email is sponsored by:Crypto Challenge is now open! Get cracking and register here for some mind boggling fun and the chance of winning an Apple iPod: http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en _______________________________________________ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
