tag:blogger.com,1999:blog-5326958204958381964.post2162493044323680714..comments2023-08-25T01:58:05.017-07:00Comments on clefru's Blog: Removing CHS based access from windows boot loadersClemens Fruhwirthhttp://www.blogger.com/profile/12793569769964183184noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-5326958204958381964.post-14614366227427255022016-07-07T01:44:46.558-07:002016-07-07T01:44:46.558-07:00This comment has been removed by a blog administrator.Mark Gallaherhttps://www.blogger.com/profile/06125642052386481475noreply@blogger.comtag:blogger.com,1999:blog-5326958204958381964.post-50399075625942376342013-04-15T11:25:10.315-07:002013-04-15T11:25:10.315-07:00Same situation here, when cloning a physical Think...Same situation here, when cloning a physical ThinkPad R60 installation (240 heads) into VirtualBox. Your patch fixed the booting so that it could get into the boot menu, where I could enable Kernel Debugging and fix the remaining two bluescreens with the help of windbg analyze plugin (first was missing IO APIC, second was a missing DLL for the AHCI implementation of VirtualBox that seemed to be different to the one used in my ThinkPad). So, if you can get into F8 menu, especially on VM where attaching a virtual serial cable is easy, try Kernel debugging :-)Unknownhttps://www.blogger.com/profile/06192597732539480187noreply@blogger.comtag:blogger.com,1999:blog-5326958204958381964.post-83829279396050535982010-12-11T23:39:57.317-08:002010-12-11T23:39:57.317-08:00Unfortunately, this does not work for a slightly d...Unfortunately, this does not work for a slightly different situation I have. I had a Thinkpad R40, which is old now. I bought a new HP Pavilion dv6t. Would love to keep the disk image from the Thinkpad. Cloned the Thinkpad disk to a USB drive (identical size) using EaseUS Disk Copy 2.3 -- disk copy, not partition copy. Then cloned the USB drive to my HP disk. There was a warning that geometries don't match -- 240 head on the USB drive vs 255 head on the HP drive -- but that EaseUS Disk Copy will handle this correctly. Checked various low level details in MBR and boot loader, and all known fixes reported on the web were indeed correctly set in the cloned version on the HP. However, HP machine does not boot -- starts the boot loader and then hangs with a blank screen and blinking cursor at top left corner. Making the changes in the bootloader per killchs.c (manually editing disk content for these 4 bytes) causes boot loader to proceed a shade more, and then it flashes what looks like MS blue screen of death; but instead of dying, the machine goes back into reboot, and I cannot capture the error message. <br /><br />Any further suggestion? Would really appreciate some help here.Let-it-be-genocidehttps://www.blogger.com/profile/14621621164301911087noreply@blogger.comtag:blogger.com,1999:blog-5326958204958381964.post-28935756336932245742009-01-11T03:07:00.000-08:002009-01-11T03:07:00.000-08:00Great, man!!I thought I'd never get my vmdk xp sys...Great, man!!<BR/><BR/>I thought I'd never get my vmdk xp system to boot directly outside Virtualbox-ose. I've spent lots of hours : installing inside, broken outside and vice versa, fixmbr, fixboot, install-mbr, dd,... Nothing worked. I knew this should be a bios question but... what to do? I'd never thought to try hexediting a boot sector (your c code doesnt accept "MSDOS5.0" system name, my boot partition, but is very clear).<BR/><BR/>* Debian Lenny package : virtualbox-ose 1.6.6-dfsg-2<BR/><BR/>ThanksVitukohttps://www.blogger.com/profile/11418670284080342764noreply@blogger.com