Mario Gzuk wrote: > Am Donnerstag, den 29.03.2007, 13:48 -0400 schrieb Michael J. Kidd: >> Nils Olav Fossum wrote: >>> Torsdag 29 mars 2007 13:40, skrev Michael J. Kidd: >>>> I modified several of the routines in init.functions... Don't use dialog >>>> at all.. Check it out. :) >>> You have probably noticed the dd error in the bootsect.dat part >>> busybox 'dd' does not support the 'conv=' parameter. >>> I just removed the conv=notrunc but I cant test it >>> because the kernel oom somehow kills the file copying... >>> >> According to http://www.busybox.net/downloads/BusyBox.html, the dd with >> busybox does support conv=notrunc... >> >> Hmm.. just looking at my linuxboot devel area.. I'm running Busybox >> 1.1.3, and I checked the coreutils/dd.c file. It does have support for >> conv w/ notrunc, sync, and noerror... So, that shouldn't be a problem. >> >> This is what I'm doing to extract the boot data from a known good drive >> / partition. ( setup w/ the dosemu method, then rebooted onto a linux >> bootable to pull the data ) >> >> Mario, can you sanity check this? >> >> Even after using the files generated with the below code, I still get >> the "Disk Error, Press any key to restart" error message... >> >> Thanks, >> Michael >> >> #!/bin/bash >> >> BASEDIR=/mnt/dd_info >> >> dd if=/dev/sda \ >> of=$BASEDIR/mbr_boot_code.bin bs=1 \ >> count=446 >> >> dd if=/dev/sda1 \ >> of=$BASEDIR/ntldr_boot_code_sector0 \ >> bs=1 count=420 skip=90 >> >> dd if=/dev/sda1 \ >> of=$BASEDIR/ntldr_boot_code_sector12 \ >> bs=512 count=1 skip=12 >> >> dd if=/c/\$win_nt\$.~bt/bootsect.dat \ >> of=$BASEDIR/binary/ntldr_boot_code_install \ >> bs=1 count=420 skip=90 > > This entry should be > dd if=$BASEDIR/binary/ntldr_boot_code_install \ > of=/c/\$win_nt\$.~bt/bootsect.dat \ > bs=1 count=420 skip=90
Uh.. are you sure? Remember.. this code is to extract the contents of the correct files on a clean drive ( done w/ Dosemu )... Not to create the bootsect.dat, but to extract the ntldr_boot_code_install file from the bootsect.dat... > > but the error seems to be in the fat partition or your partition table, > as far as i know (or i think to know,...) this error message ( "Disk > Error, Press any key to restart") comes from the mbr boot code I think, > or the bios.... so it might be that your mbr is also out of order... > Hmm... I'll dig into it more.. I tried the freedos mbr that's packaged with unattended, and I screwed up the partition table the first time ( it's 512 bytes, so I set the dd to do a count of 512.. seems that goes into partition table territory )... Set it back to the 466 count and get the same error as above. I still continue to get this error even after I extract the 466 count from a working bootable mbr, and write it back with this process. ( This is of course after the partition table has been altered and the sda1 partition has been reformatted ). I'll see if I can find a different MBR, and/or use the install-mbr.pl script from unattended... Thanks, Michael ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ unattended-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unattended-devel
