Trying to find driver for network card 5188-2907. Computer model is hp a6030n had to format drive and install xp home edition. Installing XP on 2nd Partition. By cyberghost1. Yes, it is a different version of NTFS, but apparently XP can install on it. Did you do it like this?
Learning has never been so easy!
How to install MS-DOS 6.22 alongside an existing Windows XP partition
Contents
1.1 Before we start
1.2 House-keeping
2.1 Partitioning the hard disk
2.2 Booting the original Windows partition
2.3 Original Windows partition will not boot
3.1 Creating a bootable STARTUP diskette for MS-DOS 6.0
3.2 Creating a bootable hard disk partition
3.3 Creating a Dual Boot system
4.1 Installing MS-DOS 6.22
1.1 Before we start we will need some tools. In no particular order
1. A box of 10 x 2HD 1.44Mb floppy disks
2. A computer with a floppy disk drive
3. A Hard Disk with a partition containing Windows XP or whatever you have got. Space to create a new partition of 2Gb
4. The 3 compressed floppy install disks for MS-DOS 6
5. The Stepup disks - DOS 6.0 to 6.22 - free @ http://www.microsoft.com/downloads/details.aspx?FamilyID=96cc3197-b7e5-4b31-badb-ddaac771295f&displaylang=en
6. A utility Boot.com - free from Jason Locke @ http://www.tburke.net/info/ntldr/boot.zip - can use DEBUG(MS-DOS 6.0) or DISKEDIT as an alternative(NOT recommended).
7. Norton's DISKEDIT, 1995 vintage, free @ http://vetusware.com/download/Diskedit%20NL/?id=4352
8. A floppy for NTFS4DOS - free from Avira -
http://www.free-av.com/en/products/11/avira_ntfs4dos_personal.html
Close to essential if Windows is on NTFS and anyway the best to use for FAT-32 and FAT-16
9. A way to transfer files from DOS to Windows partitions & v.v. - Windows sees the DOS partition, but the reverse is not true. The best way is using NTFS4DOS, quickest is via this floppy
10. DOS CD-ROM driver, 1995 vintage - search the web - Oak Technology. Try here - http://www.computerhope.com/download/hardware.htm
11. A disk partitioning program - Norton's Partition Magic, Powerquest's original PM, Easeus Partition
Manager and others.
1.2 House-keeping
1.2.1 Installing the Recovery Console on your Hard disk
Instructions can found @ http://support.microsoft.com/kb/307654 . This is useful if anything goes wrong.
1.2.2 Changing and making a ‘safe’ copy of the boot.ini file on the NTFS4DOS floppy
This is the file that controls the booting of the Windows partition. The file is located in the root directory of your Windows partition. Change the read-only attribute, by right clicking, selecting Properties, and removing the read-only tick. Then, we need a safe copy. Select boot.ini, ctrl-C to copy it. Place the NTFS4DOS floppy in the A: drive, select the A: drive and ctrl-V to paste boot.ini to the floppy. Do NOT change the original, boot.ini, in the root directory, back to read-only.
1.2.3 Copying a DOS editing program to the NTFS4DOS floppy
The 1st disk of the 3 MS-DOS 6 setup disks contains EDIT.COM. Copy this file to the NTFS4DOS floppy.
1.2.4 Make sure that the Windows partition is completely free of disk errors – using CHKDSK from the Command Prompt in Windows
2.1 Partitioning the hard disk
We need to create a small DOS partition on the hard disk. Theoretically, it could be 'before' or 'after' the existing Windows partition, but I have not tried it 'after'. So, we have to move the Windows partition to the right. This can be done using Norton’s Partition Magic, Powerquest's original PM, Easeus Partition Manager and others. I used Norton v. 8.05. , in particular, the DOS based Rescue diskettes #1 and #2. Shut down Windows, place the 1st diskette in the A: drive and switch on. When asked, place the 2nd diskette in this drive and get to the Partition Magic screen. Select the Windows partition and under the 'Operations' menu-item select Resize/Move. Note the current size of the Windows partition. In the Free Space Before box type 2045 Mb. and set current size of the Windows partition to be the new size. Do this task. If the Windows partition decreases in size, make it larger to be the same size before and after. Now, select the newly created partition, format it to FAT-16, label it MS-DOS60, and give it drive letter (C: ). Check both partitions with Norton's check disk facility and MS CHKDSK. Leave Norton.
2.2 Booting the original Windows partition
About this point you may have lost the ability to boot the original Windows. We should now try it. Remove all floppies from drives. If the machine is on - hit ctrl+alt+del, or if it is off, switch it on. If the machine boots successfully all is well. If not, getting it back lies with the boot.ini file in the root directory of your Windows partition. It is possible that the boot.ini file has been corrupted, by the partition move. So we should start by over-writing it with the copies made before partitioning.
2.2.1. Mending boot.ini.
Boot the system with the NTFS4DOS diskette. You will be able to select your Windows partition. Do this by typing the drive letter followed by a colon (D: ) for example, which you can get from the info on the NTFS4DOS startup screen. First, change the name of the boot.ini file on the hard disk.
REN D:BOOT.INI BOOT.OLD
Now do COPY A:BOOT.INI
That puts a copy, of our safe copy, on the NTFS4DOS floppy, back into the root directory of the Windows partition on the hard disk.
Boot the system with the NTFS4DOS diskette. You will be able to select your Windows partition. Do this by typing the drive letter followed by a colon (D: ) for example, which you can get from the info on the NTFS4DOS startup screen. First, change the name of the boot.ini file on the hard disk.
REN D:BOOT.INI BOOT.OLD
Now do COPY A:BOOT.INI
That puts a copy, of our safe copy, on the NTFS4DOS floppy, back into the root directory of the Windows partition on the hard disk.
2.2.2. Now try it.
Remove all floppies, and boot (ctrl+alt+del) or switch on. If it boots, all is well. But it suggests that moving the Windows partition might have left some corrupted files. So, intensive file checking with chkdsk, etc is called for.
If the re-boot fails there are some checks that can be made.
Remove all floppies, and boot (ctrl+alt+del) or switch on. If it boots, all is well. But it suggests that moving the Windows partition might have left some corrupted files. So, intensive file checking with chkdsk, etc is called for.
If the re-boot fails there are some checks that can be made.
2.3. Original Windows partition will not boot
2.3.1 Inspect the boot file
Boot the system with the NTFS4DOS floppy. At the prompt change to D:. Now, type
type boot.ini
The file should look like this -
Boot the system with the NTFS4DOS floppy. At the prompt change to D:. Now, type
type boot.ini
The file should look like this -
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)WINDOWS='Microsoft Windows XP Pro R0P1' /fastdetect
C:CMDCONSBOOTSECT.DAT='Microsoft Windows Recovery Console' /cmdcons
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)WINDOWS='Microsoft Windows XP Pro R0P1' /fastdetect
C:CMDCONSBOOTSECT.DAT='Microsoft Windows Recovery Console' /cmdcons
This is a lie, as the operating system no longer resides in partition (1) of rdisk (0), but partition (2). But that is way Microsoft wants it, and it will be assigned the drive letter C, when we get it to boot. The DOS partition that is the real partition (1) will get drive letter D.
Things NOT to try are rdisk(0)partition(2) that produces the well known fiction about hal.dll being missing or corrupted, neither of which is the case. I guess at this point, suicide is an option. If the boot.ini file is obviously wrong, then fix it. Make a note of the “Recovery Console” line.
Things NOT to try are rdisk(0)partition(2) that produces the well known fiction about hal.dll being missing or corrupted, neither of which is the case. I guess at this point, suicide is an option. If the boot.ini file is obviously wrong, then fix it. Make a note of the “Recovery Console” line.
2.3.2 Try Recovery Console to recover the boot.ini file
Re-boot the system and select Recovery Console. Try the command BOOTCFG in Recovery Console which will write you a new boot.ini file. If you have lost the Recovery Console line, replace it, using the NTFS4DOS floppy and EDIT.COM. Keep trying.
3.1 Creating a bootable STARTUP diskette for MS-DOS 6.0
By creating the three diskettes for the setup of MS-DOS 6.0 you can create a single bootable floppy called STARTUP which you can use to get yourself out of trouble for the rest of this journey.
3.1.1 Boot the first setup disk. The first setup diskette needs its files copied onto a bootable diskette. This can be created in Windows. Place the new floppy in the floppy drive, and in Windows Explorer right-click the A: drive and select Format. Capacity should be 3½”, 1.44MB, 512 bytes / sector. Select FAT for the File system, and Default for the Allocation unit size. Type DISK(6 spaces)1 for the Label. Do not select Quick Format and tick ‘Create a MSDOS Start Up disk’. Now click Start. Copy all the Disk1 setup files. Repeat for the 2nd and 3rd disks, except they do not need to be Start Up disks, but need labels(as above) of DISK(6spaces)2 and DISK(6spaces)3. Now boot the 1st setup disk.
3.1.2 Read the readme.txt by typing EDIT README.TXT at the prompt.
3.1.3 Set up the STARTUP diskette by executing SETUP.EXE from the 1st SETUP disk. This will be a bootable floppy with all the essential MS-DOS 6.0 files on it.
3.2 Creating a bootable hard disk partition
3.2.1 Copying all the MS-DOS 6.0 files to the hard disk. Boot the system from the STARTUP diskette. Change to the C: drive – by typing C: at the command prompt. Now we need to create some directories on the hard-drive. At the prompt type md DOS
cd DOS
md MSDOS6SU
cd MSDOS6SU
Now place the first setup disk in drive A: and type
copy a:*.*
Now place the second setup disk in drive A: and type
copy a:*.*
Now the 3rd disk, and type copy a:*.* now you have all the setup files in c:msdos6su .
Now, by typing setup you expand and copy all the DOS6 files to the C:DOS directory, as well as config.sys and autoexec.bat to the root directory.
cd DOS
md MSDOS6SU
cd MSDOS6SU
Now place the first setup disk in drive A: and type
copy a:*.*
Now place the second setup disk in drive A: and type
copy a:*.*
Now the 3rd disk, and type copy a:*.* now you have all the setup files in c:msdos6su .
Now, by typing setup you expand and copy all the DOS6 files to the C:DOS directory, as well as config.sys and autoexec.bat to the root directory.
3.2.2 Create a boot sector for the MS-DOS partition
Next we need to create a boot sector on C:. To do this type cd .. and sys c: You will also get 2 hidden files placed in C: root directory, IO.SYS and MSDOS.SYS. Finally we activate C:
Next we need to create a boot sector on C:. To do this type cd .. and sys c: You will also get 2 hidden files placed in C: root directory, IO.SYS and MSDOS.SYS. Finally we activate C:
Type fdisk Choose option 2 and select option 1 on the next screen. Now exit fdisk by pressing twice.
3.2.3 Preparing to boot from the hard disk
Look at the contents of the config.sys and autoexec.bat files, by loading them separately into the editor. For a trial boot you do not need to alter config.sys, but autoexec.bat can be usefully added to. Type
edit c:autoexec.bat
Add / change / check - the following lines
Look at the contents of the config.sys and autoexec.bat files, by loading them separately into the editor. For a trial boot you do not need to alter config.sys, but autoexec.bat can be usefully added to. Type
edit c:autoexec.bat
Add / change / check - the following lines
path c:dos; makes commands in dos always accessible
doskey /insert makes typing at the prompt easier
set dircmd= /O:GNE /A /W /P fixes the O/P of the DIR command
doskey /insert makes typing at the prompt easier
set dircmd= /O:GNE /A /W /P fixes the O/P of the DIR command
3.2.4 First hard disk boot
Remove all floppies from drives. Then press ctrl+alt+del. The system should boot and end up at C:> .
3.3 Creating a Dual Boot system
A Dual Boot system allows a choice of operating system at startup. This is controlled by the boot.ini file. For this reason the active partition is always the Windows partition. If the DOS partition were active the system would always boot the DOS partition, without any choices. In this section we will change the boot.ini file to offer a choice of Windows partition or DOS partition. To see a Windows only boot.ini file with options here is one which offers Windows as a default and, optionally, the Recovery Console from the Windows setup CD disk.
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)WINDOWS='Microsoft Windows XP Pro R0P1' /fastdetect
C:CMDCONSBOOTSECT.DAT='Microsoft Windows Recovery Console' /cmdcons
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)WINDOWS='Microsoft Windows XP Pro R0P1' /fastdetect
C:CMDCONSBOOTSECT.DAT='Microsoft Windows Recovery Console' /cmdcons
![Installing Installing](http://www.icydock.com/product/images/mb992_space_saving.png)
It offers as a second choice a file, which when executed brings up the Recovery Console.
In setting up the DOS partition, as a second choice, we will emulate this procedure.
The first piece of code that a DOS partition executes after booting resides in the boot sector of the DOS partition, so after booting we should execute a copy of this code which will lead eventually, via the hidden files in the root directory of the DOS partition, to executing config.sys and autoexec.bat., thus arriving at the DOS prompt.
In setting up the DOS partition, as a second choice, we will emulate this procedure.
The first piece of code that a DOS partition executes after booting resides in the boot sector of the DOS partition, so after booting we should execute a copy of this code which will lead eventually, via the hidden files in the root directory of the DOS partition, to executing config.sys and autoexec.bat., thus arriving at the DOS prompt.
3.3.1 Getting a copy of the DOS boot sector
This is what Boot.exe is for, which should be copied from the download directory to C:DOS. Put the NTFS4DOS floppy in drive A: At the DOS prompt execute the following line …
BOOT /R /DRIVE:C BS A:BOOTSECT.BIN
This will place a copy of the DOS boot sector in the file a:bootsect.bin, which is located on the NTFS4DOS floppy.
This is what Boot.exe is for, which should be copied from the download directory to C:DOS. Put the NTFS4DOS floppy in drive A: At the DOS prompt execute the following line …
BOOT /R /DRIVE:C BS A:BOOTSECT.BIN
This will place a copy of the DOS boot sector in the file a:bootsect.bin, which is located on the NTFS4DOS floppy.
3.3.2 Moving the file bootsect.bin to the Windows partition and editing boot.ini
Which we will do with the NTFS4DOS disk, as it can write to FAT-16, FAT-32 and NTFS partitions.
Which we will do with the NTFS4DOS disk, as it can write to FAT-16, FAT-32 and NTFS partitions.
![Installing Xp On A6030n Installing Xp On A6030n](http://1.bp.blogspot.com/--XU9KOG3hEw/UtxgMI29DOI/AAAAAAAAANU/eSyae0K1x_s/s1600/2.jpg)
Before moving on, copy the EDIT.COM file from c:dos to the NTFS4DOS floppy.
Type copy c:dosedit.com a:
Type copy c:dosedit.com a:
Boot the NTFS4DOS floppy. Type D: to change drives. Copy the a:bootsect.bin file, on the NTFS4DOS floppy to the Windows root directory (d:) with … COPY a:bootsect.bin
Now edit the boot.ini file. Type a:edit boot.ini which should look like this -
Now edit the boot.ini file. Type a:edit boot.ini which should look like this -
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)WINDOWS='Microsoft Windows XP Pro R0P1' /fastdetect
C:CMDCONSBOOTSECT.DAT='Microsoft Windows Recovery Console' /cmdcons
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)WINDOWS='Microsoft Windows XP Pro R0P1' /fastdetect
C:CMDCONSBOOTSECT.DAT='Microsoft Windows Recovery Console' /cmdcons
Add the following line just above the ‘Recovery Console’ line
c:bootsect.bin=“ Microsoft MS-DOS 6.0 “
Save the changes by typing - + F, X and then Y.
Note: When dual-booting, the Windows partition will be C:. NOT D:
c:bootsect.bin=“ Microsoft MS-DOS 6.0 “
Save the changes by typing - + F, X and then Y.
Note: When dual-booting, the Windows partition will be C:. NOT D:
3.3.3 Try the DUAL BOOT
Remove all floppies and press ctrl+alt+del. If you get the new dual boot option select Windows or DOS and press ENTER. If NOT and we boot straight to a DOS prompt, with no Dual Boot options, the DOS partition is active, and we must change that.
At the DOS prompt, type FDISK then, select option 2. At the next screen, you have to select the Windows partition as active. This will be #2. It will be of Type Non-DOS or HPFS and almost certainly have a negative size, because DOS 6.0 cannot read an NTFS partition. Anyway select partition 2. Press twice to exit FDISK, and reboot. This time you should get the DUAL BOOT choice. If it again boots to a C: prompt it will be because the Windows partition has been hidden. Although the Windows partition, if it is XP, has no need of this, MS does it anyway, because Windows 2000, Win ’98 and Win NT get upset. This situation requires the intervention of Norton. Boot the Norton PM disks, select the Windows partition, and check that it is Active and NOT hidden. If you have an XP Windows make the 1st (small) partition inactive (it should be already) & visible. DO all of these things. That should solve it.
At the DOS prompt, type FDISK then, select option 2. At the next screen, you have to select the Windows partition as active. This will be #2. It will be of Type Non-DOS or HPFS and almost certainly have a negative size, because DOS 6.0 cannot read an NTFS partition. Anyway select partition 2. Press twice to exit FDISK, and reboot. This time you should get the DUAL BOOT choice. If it again boots to a C: prompt it will be because the Windows partition has been hidden. Although the Windows partition, if it is XP, has no need of this, MS does it anyway, because Windows 2000, Win ’98 and Win NT get upset. This situation requires the intervention of Norton. Boot the Norton PM disks, select the Windows partition, and check that it is Active and NOT hidden. If you have an XP Windows make the 1st (small) partition inactive (it should be already) & visible. DO all of these things. That should solve it.
4.1 Clean-up and installing MS-DOS 6.22
4.1.1 Installing MS-DOS 6.22. There are 3 floppies for this. If ‘STEPUP’ was downloaded, the self-extracting executable file STEPUP.EXE is in the download directory. It is easier to do the installation from the hard disk. Make a sub-directory of C:DOS called STEPUPSU and copy the following files to STEPUPSU from the floppies, or, copy STEPUP.EXE(from the download) to it and execute it.
The files to copy are 1MSDOS62.EXE, 2MSDOS62.EXE, 3MSDOS62.EXE, DBLCDESC.TXT, DBLCONV.EXE, DESCRIP.TXT, NEW4_622.TXT, README.NOW, SETUP.BAT, and STEPUP.EXE.
Now you should read all the .TXT files using EDIT.COM or TYPE |MORE and follow the instructions. At the end of this procedure you should have MS-DOS 6.22 successfully installed.
The files to copy are 1MSDOS62.EXE, 2MSDOS62.EXE, 3MSDOS62.EXE, DBLCDESC.TXT, DBLCONV.EXE, DESCRIP.TXT, NEW4_622.TXT, README.NOW, SETUP.BAT, and STEPUP.EXE.
Now you should read all the .TXT files using EDIT.COM or TYPE |MORE and follow the instructions. At the end of this procedure you should have MS-DOS 6.22 successfully installed.
4.1.3 Checking the ‘DUAL BOOT’. Floppies out, and boot the system, selecting Windows. We need to edit boot.ini, with Notepad to change the line “ Microsoft MS-DOS 6.0 “ From …
c:bootsect.bin=” Microsoft MS-DOS 6.0 “ to c:bootsect.bin=” Microsoft MS-DOS 6.22 “
Now, change boot.ini to “Read-Only”. Re-boot, this time choosing MS-DOS 6.22. Should work!!
c:bootsect.bin=” Microsoft MS-DOS 6.0 “ to c:bootsect.bin=” Microsoft MS-DOS 6.22 “
Now, change boot.ini to “Read-Only”. Re-boot, this time choosing MS-DOS 6.22. Should work!!
4.1.4 Making MS-DOS 6.22 work. There is more to this than meets the eye. But all the instructions and tools are there. Firstly, there is the HELP command. Try it. Then, most executable files respond to the /? Switch. Try this with, say, PATH /?. This gives a short version of what it does while HELP PATH gives the longer version. The two files CONFIG.SYS and AUTOEXEC.BAT will get most of your attention. They execute just before the appearance of the first system prompt. CONFIG.SYS loads most of the drivers you will need, it is concerned with keyboards, screen setup, memory, hardware, language, country etc., and, AUTOEXEC.BAT handles the pre-setup for running the basic system. There is some overlap in these responsibilities, and a lot for you to do. I recommend carefully reading all about memory management – himem.sys, emm386.exe, memmaker.exe - and using mem /c & mem /d. Getting most of the drivers to load into Upper Memory, leaving the maximum amount of conventional memory for programs, is a real trick. You should strive for 600K bytes free. Having 1 - 2 gigabytes of memory in the machine won’t save you. It is what is free below 640K that matters.
4.1.5 Simple examples of CONFIG.SYS and AUTOEXEC.BAT for MS-DOS 6.22
CONFIG.SYS
DEVICE=C:DOSHIMEM.SYS /TESTMEM:OFF /V
DEVICE=C:DOSEMM386.EXE NOEMS HIGHSCAN I=B000-B7FF NOTR /V
BUFFERS=10,0
FILES=40
DOS=UMB
LASTDRIVE=H
FCBS=1,0
NUMLOCK=OFF
BREAK=ON
DOS=HIGH
STACKS=0,0
DEVICEHIGH /L:2,28864 =C:DOSEXTRASOAKCD1.SYS /D:CD-ROM
DEVICEHIGH /L:2,3744 =C:DOSRAMDRIVE.SYS 2048 512 256 /E
SHELL=C:DOSCOMMAND.COM C:DOS /E:1024 /P
DEVICE=C:DOSEMM386.EXE NOEMS HIGHSCAN I=B000-B7FF NOTR /V
BUFFERS=10,0
FILES=40
DOS=UMB
LASTDRIVE=H
FCBS=1,0
NUMLOCK=OFF
BREAK=ON
DOS=HIGH
STACKS=0,0
DEVICEHIGH /L:2,28864 =C:DOSEXTRASOAKCD1.SYS /D:CD-ROM
DEVICEHIGH /L:2,3744 =C:DOSRAMDRIVE.SYS 2048 512 256 /E
SHELL=C:DOSCOMMAND.COM C:DOS /E:1024 /P
AUTOEXEC.BAT
@echo off
LH /L:1,26224 C:DOSMSCDEX /D:CD-ROM /M:15 /E /S /L:D /V
LH /L:2;1,8208 /S C:DOSSMARTDRV A- B- C+ E /B:8192 /V
LH C:DOSDOSKEY /INSERT
PROMPT=$p$g
PATH C:DOS;C:MENU;C:BP;C:ZIPS
SET COMSPEC=C:DOSCOMMAND.COM
SET DIRCMD= /O:GNE /A /W /P
SET BLASTER=A220 I5 D1 T1
SET TEMP=C:TEMP
SET TMP=C:TEMP
VER /R
LH /L:1,26224 C:DOSMSCDEX /D:CD-ROM /M:15 /E /S /L:D /V
LH /L:2;1,8208 /S C:DOSSMARTDRV A- B- C+ E /B:8192 /V
LH C:DOSDOSKEY /INSERT
PROMPT=$p$g
PATH C:DOS;C:MENU;C:BP;C:ZIPS
SET COMSPEC=C:DOSCOMMAND.COM
SET DIRCMD= /O:GNE /A /W /P
SET BLASTER=A220 I5 D1 T1
SET TEMP=C:TEMP
SET TMP=C:TEMP
VER /R
On my machine this gives the following available memory:-
Conventional (below 640K) 611,448 bytes
Upper (above 640K & below 1024K) 3,856 bytes
Extended (XMS) 61,485,056 bytes
Largest executable program size 611,344 bytes
Cache buffer for C drive & CD-ROM
RAM memory drive with 256 file entries 2048 K bytes
Conventional (below 640K) 611,448 bytes
Upper (above 640K & below 1024K) 3,856 bytes
Extended (XMS) 61,485,056 bytes
Largest executable program size 611,344 bytes
Cache buffer for C drive & CD-ROM
RAM memory drive with 256 file entries 2048 K bytes
4.1.6 SAFETY You should move BOOTSECT.BIN from the NTFS4DOS floppy to a safe place.
Published: Apr 17, 2010 · Last Updated: Apr 19, 2012
4 Comments
- SerranoCezaryG Apr 23, 2010 at 03:54amI use this method for dual boot system.
1. Install WXP
2. Use PQmagic (or another partition software) and resize partition to leave space for DOS, move WXP to the end of disk, create new fat partitiion for DOS in the front of WXP and set it active. Save all changes and restart computer.
3. Boot with DOS floppy disk (I use external USB floppy drive) and start setup MS-DOS or just run format c:/s if you don't need DOS tools.
4. Activate WXP partition with PQmagic or fdisk.
5. Make dual boot with BootPart (http://www.winimage.com/bootpart.htm)Regards
Cezary - JalapenoScandalon Jan 13, 2012 at 06:20pmMay I ask why? (Besides that it's a fun project.) Are you doing some sort of embedded development or something that needs DOS access to the hardware? I'm guessing that 98% of the people that want this could just use a VM...http://www.microsoft.com/windows/virtual-pc/download.aspx
https://www.virtualbox.org/ - AnaheimPaul8904 Apr 19, 2012 at 11:22amWhoa! That took me back a decade+
- Pimientoxxxxxxxxxxx Feb 18, 2013 at 09:42pmMy thoughts exactly Scandalon. Except I was sort of whimpering and crying at the same time i was asking myself that in my head...