Mandag 14 april 2008 15:05, skrev Juan Jose Pablos: > Hi, > I am wondering if I am the only one that is getting this problem. Since > we update to 1.8.8 I see more systems with this error. I go back to 4.7 > and they work fine.
hm, that is strange. The reason I added the ntldr-fix was the 'ntdlr not found' situation we had pre 4.7 What kind of machines is this? (chipset, maker) And, yes there are only two error messages: NTDLR not found and something about corrupt something And, yes they are in german, as I used what Mario had on site :-) > > So either people is not testing/trying out, or I have something wrong on > my env. Im sure the ntldr-fixing is working, as we are at the end of a thinkpad T61 pushout here. (On one of them I had to zero the mbr/partiton tabe to get it installed, but that was never starting the ntldr code.) There may be hardware that are reporting wrong geometry via the EDD kernel module out there, or something else goes wrong. You can see what disk geometry unattended reads from EDD on bootup, and that is what is being written to disk as well. If youre hardware needs other values, you can set them from unattend.txt oh, yes, some BIOS reports disk geometry from whats on disk! you can also use "replace_mbr = 1" and see if that works, but I dont think it will. ------------------------------------------------------------------------- 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
