Mail Archives: djgpp/2003/01/21/05:00:22.1
> >If your DOS supports FAT32, you'll get asked whether you want to enable
> >large disk support when you run FDISK.
OK. I found out that I was wrong about that. FreeDos FDISK asks whether to
enable Large Disk Support, yet FreeDos does not support Large Disk Support.
> I think, this is a bug un the german Version of
> msdos 6.22.
OK. Since you're using DOS 6.22, you should be able to create compressed
volumes with DRVSPACE.EXE, which comes with DOS 6.22. By default, I think
these compressed volumes have 16 sectors/cluster, yet it can compress down
to about 1 saector per cluster (with 16:1 compression, the maximum
compression the DriveSpace that comes with DOS 6.22 supports). I'm talking
about the 'virtual' clusters on the compressed volume, and not the real
clusters on the physical partition.
A DriveSpace compressed volume can be up to 2GB in size, as it is FAT16.
> I have the Win95B WITH Licence but I do not like to use it...
>
> Hmm, any suggestions how to install only the DOS 7.0 ???
> It will solve all problem in one time...
>
> In theory I need only the Dos-Files and a Dos-Bootable Floppy,
> which can partition and format it with FAT32 then I can copy all
> DOS 7.0 files to the directory and reboot.
>
According to what I read, Win95B comes with DOS 7.10
It shouldn't be too hard to get a FAT32 drive using the DOS
7.10 that comes with Win95B.
Just SYS the primary partition (C:) from the Win95B boot floppy, then ensure
the following files are in your path in the AUTOEXEC.BAT file:
FDISK.EXE
FORMAT.COM
SYS.COM
DEBUG.EXE
These files must be from Win95B, as DOS up to and including DOS 7.0 do not
support FAT32.
Then reboot.
It would be a good idea to zip-up all of your important files on drive C or
something, as all of the data on the drives under the extended partition
will be lost.
Then run FDISK.
When it asks whether you want to enable large disk extensions, say yes.
Delete all of the logical drives under the extended partition, then create a
new logical drive, using all of the space in the extended partition. This
partition should be a FAT32 partition, since it is greater than 512MB in
size. If it is not, then you'll have to use DEBUG or a real-mode assembler
or a real-mode disassembler that allows you to type in code.
If the new partition is not FAT32 (it should be), you'll have to type the
following (assuming DEBUG):
<Start of typing>
A 0100
MOV AX,0201
MOV BX,0200
MOV CX,1
MOV DX,080
PUSH CS
POP ES
INT 13
MOV CX,WORD PTR [03D0]
MOV AX,0201
INT 13
MOV BYTE PTR [03C2], 0B
MOV AX,0301
INT 13
INT 20
G
Q
<End of typing>
This will change the partition type to FAT32.
After the FDISK and possible DEBUG, reboot.
After this is done, FORMAT the drive (D:)
If it is indeed FAT32, there should be more than 128k clusters reported.
Now, chack that you can access the drive.
Once successful, you can un-zip all of the files to D: drive, with directory
structure intact.
I'd suggest you go with DRVSPACE if you don't want to play with fire.
Otherwise, if you're not careful, you might get burnt.
- Raw text -