Date: Thu, 31 May 2007 13:39:23 +0930 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: freebsd-hackers@freebsd.org Subject: boot0 vs XP Message-ID: <200705311339.37683.doconnor@gsoft.com.au>
next in thread | raw e-mail | index | archive | help
--nextPart147574748.L9FOGiGbBa Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I recently reinstalled Windows XP on my laptop (I barely use it but=20 occasionally it comes in handy :) and when I did the install it made=20 the base drive E (no idea why, and I couldn't see how to change it). Everything proceeds as usual and then I boot a CD to then jump start my=20 system and run boot0cfg to re-write the boot loader. Alas the next time I boot Windows it logs me out straight after logging=20 in. I do some googling and find that it is most likely that the=20 signature bytes Windows uses to determine which drive is what have=20 changed and it has now made the drive C:. Hence the swapfile location=20 is now incorrect :( I was wondering if it would be possible to modify boot0cfg (and boot0 I=20 guess) so that it avoids touching these bytes. I found some details here ->=20 http://www.goodells.net/multiboot/partsigs.htm Basically it would appear to be the 4 bytes just before the partition=20 table. I'm not sure how big boot0 is though :) =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart147574748.L9FOGiGbBa Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQBGXkqB5ZPcIHs/zowRAgs3AKCDO0dU6nIaJ0cABv1bea+tSQ44CwCePmaG rCyFyZipLsjPhhwfAJ/Ts/k= =KUvL -----END PGP SIGNATURE----- --nextPart147574748.L9FOGiGbBa--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200705311339.37683.doconnor>