Luciano Moretti <[EMAIL PROTECTED]> writes: > I'm trying to get Unattended 3.5 working for my systems. On my test > box everything seemed to work fine, and I selected the "Use Whole > Disk" setting. > > Now on reboot, I get the error message "fdisk /info /tech > \tmp.txt > Failed, unexpected status 5 at (Line number- sorry.. I missed > writing it down) in Z:\dosbin\install.pl"
Well that's not good. What kind of system is this, exactly? (In particular, what sorts of drives are connected?) This error means that fdisk itself is bombing out, so we need to figure out why. After the crash, you should be at a DOS prompt. Please try running "fdisk /info /tech" by hand; it should provide some sort of diagnostic. One thing you can try is selecting "No large disk support (required for some broken BIOSes)" at the first prompt. Since you are using the whole disk, this will actually not make any difference in the end; it only matters if you want to partition the drive in a complex way. - Pat ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
