On Tue, Apr 29, 2008 at 10:57:17PM +0200, Mario Gzuk enlightened us: > Am Dienstag, den 29.04.2008, 15:24 -0400 schrieb Matt Hyclak: > > On Tue, Apr 29, 2008 at 03:08:33PM +0100, Sid Brydon enlightened us: > > > Is anyone getting any further with this issue, I have tried all the > > > variations that I can think of, changing the geo_heads and geo_sectors > > > options but it keeps failing with the NTDLR not found error (depending > > > what > > > options I use this can be in English or German). > > > > > > Regards > > > Sid > > > > > > > I just hit my first instance of this with today's CVS and a machine that is > > also reporting 78 heads and 60 sectors. I have an intel board with a SATA > > drive (80 GB, I think) connected. > > > > I'm not sure what the solution is, if any, at this point. > > > > Nils? Mario? Any more thoughts? Do we drop back to 1.6.22? > > > > Matt > > .... > The ntldr not found is not only related to the heads and sectors in the > fat partition. Simple read point 3) here: > http://unattended-gui.sourceforge.net/index.php?title=Win:installation_process > > So it can also be that the bootsect.dat is corrupt... > > If I should help simple send me the bootsect.dat, the first 12 sectors > from the fat partition and optional the mbr from the affected system. > Also it could be helpful if you run a simple XP-CD installation and stop > after the first reboot to get the same informations. > > Also a shourt description of the system would be helpfull. (mainly > ide/sata controller and harddisk type, size and producer) > > We use parted 1.6.22 together with the fix-heads/sectors and I cant > remember that we have problems since this combination. We also have a > zoo of hardware like Dell (Latitude/OptiPlex), Lenovo and also self > screwed systems... > > An other way might be a little bit better: use a ntfs FS! This will not > work with the dosemu (or is there a driver available to write to ntfs? I > dont know), but if you use ntfs-3g and the nt5install stuff it should > work with some little modifications because the boot code in the ntfs is > different to FAT... > The boot code from ntfs is located in the first sektor from byte 85-7680 > > take a look at point 2) here: > http://unattended-gui.sourceforge.net/index.php?title=Win:installation_process_vista > Its nearly the same, but you should use the boot code from XP... >
I'm not real sure what happened, but after using my old boot disk (which uses winnt.exe and parted 1.6.22), edd now reports 255/63 even with the new boot disk. I wonder if switching to ntfs-3g isn't the way to go with this... Matt -- Matt Hyclak Department of Mathematics Department of Social Work Ohio University (740) 593-1263 ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ unattended-devel mailing list unattended-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-devel
