Gerry Hickman schreef:
In the above case, Windows will replace the DOS 6.22 boot sector and
will not try to offer any "previous" o/s on the boot loader menu
(BOOT.INI) when Windows has finished installing.
allright. This case was clear.
You've created a booting/working DOS6.22 system by whatever means,
then after that you start the Windows setup.
However, when using FreeDOS's [FDISK FAT32 FORMAT (not with /s)] to
create the C: drive, Windows suddenly decides there's a "previous o/s"
and backs up it's boot sector and then creates a "boot loader" menu with
30 second time-out (BOOT.INI). This is the last thing you need when
creating automated hands-free builds! I think the reason is because
FreeDOS's boot-sector from FORMAT is not the same as that of MS-DOS, so
Windows does not recognize it as an "upgradable" Microsoft o/s.
MS FORMAT's bootsector is the same as that from MS SYS.
FD FORMAT's bootsector is a pure message which says: "this disk isn't
bootable"
FD SYS (v3.6)'s bootsector can be configured to work on multiple
operating systems:
-FDOS : fat12, fat16, fat32
-MSDOS: fat12, fat16 (no MSDOS supports FAT32)
-DRDOS: fat12, fat16 (perhaps fat32?)
-Win9x: fat12 (fat16/fat32 not working yet)
Today I tried the following, note use of FreeDOS SYS
(hard drive already has an MBR, DellDiags are on first primary but are
not an issue, they're always there)
1. FDISK /DELETE:2 (get rid of WinXP NTFS on second primary)
2. FDISK /PRI:2000
3. FDISK /ACTIVATE:2 (make new second primary active)
<reboot>
3. FORMAT C: /a (4k cluster size)
4. SYS a: c: BOOTONLY (put FreeDOS bootsector onto c: drv)
5. Start Windows real-mode setup program
check 'SYS /?' to see if you need
SYS A: C: BOOTONLY
-or-
SYS A: C: /BOOTONLY
this was changed in revisions, which is why SYS 3.6 isn't official yet.
Also between step 4 and 5 I would like you to check if MSDOS 6.22 boots
properly from the partition.
It doesn't matter which programs you use to create a working MSDOS 6.22
system, just make sure to get this working system before doing an
attempt to see if dualboot will be created or not by Windows.
just copy IO.SYS, MSDOS.SYS and COMMAND.COM to C:,
then do SYS A: C: /BOOTONLY /OEM:MS
and reboot system.
Then check if MSDOS boots first, and only when it does,
install Windows.
SYS A: C: /BOOTONLY /OEM:MS
installs a non-MS bootsector which actually works with MSDOS system
files. I want to see if this tricks Windows in not creating a dualboot
environment.
As an experiment (before this last step) I decided to use FreeDOS SYS to
replace the "broken" NT boot sector to see if it would fix it. FreeDOS
SYS has an option to grab a 512b boot sector from a file and write it to
a drive (very nice), so I got an official Win2k boot sector into a file
called bootsect.bin and told SYS to install it to the C: drive, and even
told it to use NTLDR instead of FreeDOS KERNEL.SYS
SYS has a /BACKUPBS option, and probably a /SAVEBS and /RESTOREBS function.
bootsect.bin is usually a 2048bytes bootsector for creating a new
bootable windows installation cdrom. harddisk bootsectors are 512bytes.
I might start testing myself if I'm bored enough :)
Bernd
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
