Msdos Boot CD 1.4 MB limit

  • Thread starter Thread starter Renob Egral
  • Start date Start date
R

Renob Egral

Once upon a time I created an Msdos boot CD that had all my chosen utilities on it. This CD no longer works and needs to be
recreated. The only problem is I can't make one that holds more than 1.4 MB of data and I know there's a reason why and I know there's
a fix for it, however I can't remember either. What do I need to do to make an Msdos boot CD hold about 50 MB of my data?
 
Once upon a time I created an Msdos boot CD that had all my chosen utilities on it. This CD no longer works and needs to be
recreated. The only problem is I can't make one that holds more than 1.4 MB of data and I know there's a reason why and I know there's
a fix for it, however I can't remember either. What do I need to do to make an Msdos boot CD hold about 50 MB of my data?

Your on about a floppy?? A floppy holds 1.44mb. (2mb on "double
sided") a CD will hold 700+mb. What platform boot floppy do you want?
I still have them all. Well, most of them. :-)
 
In message <[email protected]> "Renob Egral"
Once upon a time I created an Msdos boot CD that had all my chosen utilities on it. This CD no longer works and needs to be
recreated. The only problem is I can't make one that holds more than 1.4 MB of data and I know there's a reason why and I know there's
a fix for it, however I can't remember either. What do I need to do to make an Msdos boot CD hold about 50 MB of my data?

If you're using a floppy image embedded on the CD, you're essentially
creating two partitions on the CD, one that will appear as a floppy, and
a second that mounts as a normal CD.

The second is only available once you load the appropriate driver and
MSCDEX.EXE.
 
Once upon a time I created an Msdos boot CD that had all my chosen utilities on it. This CD no longer works and needs to be
recreated. The only problem is I can't make one that holds more than 1.4 MB of data and I know there's a reason why and I know there's
a fix for it, however I can't remember either. What do I need to do to make an Msdos boot CD hold about 50 MB of my data?

The legacy choice was to use a DOS oriented image that loads
CDROM drives so the rest was accessible on a second logical
drive volume, second drive letter.

I belive there are other ways to avoid this, maybe using a
Bart's BootCD (google for it), but frankly I try to avoid
all this by using bootable compact flash, whether that be a
USB thumbdrive for systems that support it, or just popping
the side off and plugging in an IDE-CF adapter board for
legacy systems that don't.
 
In message <[email protected]> "Renob Egral"



If you're using a floppy image embedded on the CD, you're essentially
creating two partitions on the CD, one that will appear as a floppy, and
a second that mounts as a normal CD.

The second is only available once you load the appropriate driver and
MSCDEX.EXE.

Large Boner is obviously going on about a floppy. He says,"What do I
need to do to make an Msdos boot CD hold about 50 MB of my data?" What
kinda CD DOESN'T have room for 50MB???? He's a flake if you ask me.
 
Once upon a time I created an Msdos boot CD that had all my chosen utilities on it. This CD no longer works and needs to be
recreated. The only problem is I can't make one that holds more than 1.4 MB of data and I know there's a reason why and I know there's
a fix for it, however I can't remember either. What do I need to do to make an Msdos boot CD hold about 50 MB of my data?

assuming drive lettering you would have given NTFS drives - they are
not recognised in drive letters by DOS.

After booting the CD, it goes to A: which probably just allows
1.44MB

Try typing



D: <ENTER>
I guess that would be the read-only CD. (easy to find out - "edit
a.txt, type stuff, try to save" ERROR!!.. or "copy con a.a , type
stuff , CTRL-Z " and I think that says 0 bytes free).

But the CD does create a RAM drive..

Would be C
try C: <ENTER>
do DIR <ENTER> if it has stuff you don`r recognise as being your hard
drive, then it would be the RAM drive. And it may say that something
like the volume label is RAM Drive, if you do DIR then at the top it
should say that. dir /p may help.
How much can you put there? no doubt more than 1.44MB !

C: is a RAM drive it creates. So data put there will vanish. But you
will be able to put a fair amount there. Prob more than 50MB..

You can burn 600/650/700/800 MB of data on the 600/650/700/800MB CD-R
when you burn the CD. That will go on the CD itself, D: - read only

But if you want to use the CD like a big floppy, i.e. you want to be
able to boot from it and add to it and have it stay there, then you
should look at booting from a USB Key.
 
or just popping
the side off and plugging in an IDE-CF adapter board for
legacy systems that don't.

you prefer that to plugging a HDD in ?

if it uses 2.5" IDE, then a 2.5" HDD, no adaptors necesssary, is
fairly small anyway!

Do you just prefer CF/compact flash used in this way to a HDD, `cos
it`s smaller than a hard drive?
 
you prefer that to plugging a HDD in ?

yes, because you have to have a place to put that HDD, the
cable may not be long enough to keep other drives plugged in
or to reach down to the tabletop, then there's screwing it
down or sometimes having to even pull out cards to get
access to the HDD bay, or pulling off a front cover plate,
etc.

With the CF card plus adapter so small, and that it requires
so little power that a long power extension can be used
without issue of dropping voltage or pulling too much
current on a wiring harness that was already powering other
things... it just offers all-around better usability except
for the area of speed, but seldom is one needing this kind
of speed for small utility/etc access where one would be
booting a CD instead, which isn't exactly fast either, or
even worse a floppy.


if it uses 2.5" IDE, then a 2.5" HDD, no adaptors necesssary, is
fairly small anyway!

Since there was no mention of it being a notebook, it seems
less likely to support 2.5" IDE. Perhaps you meant 3.5",
but either way a CF card plus adapter is inexpensive and so
small and lightweight it can literally be left dangling from
the cable plug, not mounted at all. I did not just start
out using CF cards for this, rather I found it far faster
and more convenient.


Do you just prefer CF/compact flash used in this way to a HDD, `cos
it`s smaller than a hard drive?

For the purpose, a hard drive has no benefit... unless one
is talking about moving around files large enough to make
the CF card too small or too expensive such as making or
restoring a system backup. Certainly CF card is not going
to cover every possible situation but for the stated purpose
of replacing a boot CD, capacity 700MB or less, it will do
fine AND it gets around some other issues with legacy
systems that may not support the capacity of a larger modern
(new enough to be working and dependable) hard drive.

I'd prefer to boot a USB thumbdrive instead, but not all
systems can do it even if they're supposedly able to.
Fortunately it is more and more common today that systems
can actually accomplish it.
 
DevilsPGD said:
In message <[email protected]> "Renob Egral"


If you're using a floppy image embedded on the CD, you're essentially
creating two partitions on the CD, one that will appear as a floppy, and
a second that mounts as a normal CD.

The second is only available once you load the appropriate driver and
MSCDEX.EXE.


Wonderful, just what I needed!
Thank you!
 
kony said:
The legacy choice was to use a DOS oriented image that loads
CDROM drives so the rest was accessible on a second logical
drive volume, second drive letter.

DevilsPGD beat you by a couple hours, a little kick in the butt was all I
needed to move forward.
I belive there are other ways to avoid this, maybe using a
Bart's BootCD (google for it), but frankly I try to avoid
all this by using bootable compact flash, whether that be a
USB thumbdrive for systems that support it, or just popping
the side off and plugging in an IDE-CF adapter board for
legacy systems that don't.

I've never used Bart's BootCD, I'll check it out. I have a CFIDE adapter and
it works fine for this, but such devices aren't allowed on the medical
domain at work.

Thank you!
 
yes, because you have to have a place to put that HDD, the
cable may not be long enough to keep other drives plugged in
or to reach down to the tabletop, then there's screwing it
down or sometimes having to even pull out cards to get
access to the HDD bay, or pulling off a front cover plate,
etc.

With the CF card plus adapter so small, and that it requires
so little power that a long power extension can be used
without issue of dropping voltage or pulling too much
current on a wiring harness that was already powering other
things... it just offers all-around better usability except
for the area of speed, but seldom is one needing this kind
of speed for small utility/etc access where one would be
booting a CD instead, which isn't exactly fast either, or
even worse a floppy.




Since there was no mention of it being a notebook, it seems
less likely to support 2.5" IDE. Perhaps you meant 3.5",
but either way a CF card plus adapter is inexpensive and so
small and lightweight it can literally be left dangling from
the cable plug, not mounted at all. I did not just start
out using CF cards for this, rather I found it far faster
and more convenient.




For the purpose, a hard drive has no benefit... unless one
is talking about moving around files large enough to make
the CF card too small or too expensive such as making or
restoring a system backup. Certainly CF card is not going
to cover every possible situation but for the stated purpose
of replacing a boot CD, capacity 700MB or less, it will do
fine AND it gets around some other issues with legacy
systems that may not support the capacity of a larger modern
(new enough to be working and dependable) hard drive.

I'd prefer to boot a USB thumbdrive instead, but not all
systems can do it even if they're supposedly able to.
Fortunately it is more and more common today that systems
can actually accomplish it.

This is fantastic information, since I like noiseless fanless
machines, and I have an old machine fanless VIA EPIA, with a newer "
PicoPSU " fanless 120W PSU. And the only thing making a noise was the
hard drive.. I cannot boot from USB on it.
More serious systems (with hard drives!), like with data I want on
them, can be kept - boxes downstairs, with a KVM Extender.. This is
quite a finding. Many thanks.
I bought the old system VIA EPIA in 2003. I was unable to use it
because the power supply cards at the time made a high pitched noise.
Then in early 2007 I found they sold these PicPSUs, they do not make
a high pitched noise - great. But I still had the HDD issue.. Now
that is solved!
 
This is fantastic information, since I like noiseless fanless
machines, and I have an old machine fanless VIA EPIA, with a newer "
PicoPSU " fanless 120W PSU. And the only thing making a noise was the
hard drive.. I cannot boot from USB on it.

I'm a little surprised you can't boot USB, though I vaguely
recall one Via C3 based board I have (not EPIA but a similar
PCChips version) had to have the USB thumbdrive formatted to
FAT16, and set to RMD-Floppy or something like that in the
bios... but this was easy enough to figure out because
pressing F8 before the system tried to boot a drive would
bring up a boot menu that listed everything it found and the
type of device it was considered.
More serious systems (with hard drives!), like with data I want on
them, can be kept - boxes downstairs, with a KVM Extender.. This is
quite a finding. Many thanks.
I bought the old system VIA EPIA in 2003. I was unable to use it
because the power supply cards at the time made a high pitched noise.
Then in early 2007 I found they sold these PicPSUs, they do not make
a high pitched noise - great. But I still had the HDD issue.. Now
that is solved!

Keep in mind that I use CF-IDE mostly for installation or
utilities, not running the OS (though i have done so in the
past). For (windows/etc) OS the CF card can be rather slow
unless you're using a fairly modern CF3.0 spec'd card and
the IDE adapter supports DMA. This is important to get it
out of PIO mode which limits it to about 6MB/s.

Note that some cards may occasionally be listed as only "CF
spec" or similar but they dont' come out and say which
version of the spec. You'd want CF3 or CF4 spec for fast
cards with this support. On the other hand if you just want
to get the job done as cheaply as possible, these days an
older PIO mode 2GB card can be had for under $15 and a
cheapie eBay CF-IDE adapter for about $3 + S/H.

It is pretty great just how low power consumption can be
using a CF card. I have a NAS enclosure on my desk that I'm
playing around with, which can also webserve and do P2P. I
temporarily put a CF card in it and it now consumes about
3.8W booting, 2.6W idle. It'd take more than that just to
power the hard drive.
 
Using Nero express ver. 5 I can either:
Create a boot CD using a floppy as the boot image. The boot partition will be 1.4 MB and the rest of the CD can be accessed as a normal CD, which require CD drivers to be loaded.
Create a hard drive partition of 700 MB. Use this hard drive partition as the boot image so that the entire CD can be accessed without CD drivers.
 
I'm a little surprised you can't boot USB, though I vaguely
recall one Via C3 based board I have (not EPIA but a similar
PCChips version) had to have the USB thumbdrive formatted to
FAT16, and set to RMD-Floppy or something like that in the
bios... but this was easy enough to figure out because
pressing F8 before the system tried to boot a drive would
bring up a boot menu that listed everything it found and the
type of device it was considered.

Interesting, I just checked, I do not have that problem.. (and my BIOS
- phoenix BIOS - does have an option for USB-HDD, and no RMD-Floppy
option). I figured my MBRD just did not support it.
But
Turns out it is fine,, same as my other very different machine. I do
not know why it did not boot off USB "last time"(I had only tried it
on one day, must have done something wrong that day).

BTW, OT, The VIA EPIA it seems had 2 processor options. C3 and EDEN.
C3 was faster but had a fan. I chose EDEN, which was fanless. Anyhow,
back onto the USB thing.


I did run into a problem booting USB, which I have isolated somewhat.

ntoe- I have not retested this.. But I am fairly sure I did not slip
up in these tests.

HPUSBFW.EXE (the famous program by HP, for formatting a usb key), has
an option to either format as FAT32, or instead, to format as what it
calls "FAT". )

(I know that at one time, prior to FAT32. You had FAT16 and FAT. FAT
was considered to be FAT12. But nowadays, you have FAT32, FAT16, and
FAT12. But FAT12 is not mentioned much, and FAT tends to refer to
FAT16).

Windows does not say whether by FAT, it means FAT12 or FAT16.
So looking at a USB key, one cannot see that way with Windows which it
is.

However.. FAT16 has a 2GB limit
16 bits for addresses, some size per address. (2^16 * x = 2GB ) x
happens to equal 32K (2^5=32K). But it is easier to remember the 2^16
and the 2GB !

FAT12 has a 2MB limit (1.44MB when formatted.)
2^12 * 512K = 2MB
FAT12 is used for floppy disks.

I noticed that HPUSBFW.EXE when told to format as FAT, was formatting
disks > 2GB as FAT16, and they were still > 2GB in available
capacity.

And those USB keys, > 2GB , formatted as what HPUSBFW.EXE called FAT,
do not boot. (they do view in windows xp though, but that is
irrelevant)

Whereas USB Keys formatted by HPUSBFW.EXE as FAT32, do boot.
And those USB keys < 2GB, boot, even if formatted as what HPUSBFW.EXE
calls FAT - which is no doubt FAT16. Do boot.

The ones that fail/"do not boot", crash both my very different
computers, at the point in the BIOS, where it says Verifying DMI pool
data

One program that does display whether FAT16 or FAT12 is FDISK.. When I
booted off a USB key that booted. (a < 2GB USB key, formatted as
FAT16). FDISK saw it - as DOS does. And it said FAT16. So that
verifies that when HPUSBFW.EXE says FAT, it means FAT16. But it is
some mangled FAT16 when the drive is > 2GB.

Or perhaps not mangled.. but some Windows limit (and perhaps limit
from some or all BIOSs) on the "cluster size" with FAT16
Windows limit is not that relevant, but as a related note
and also, note that the USB keys I tried > 2GB, were 4GB
http://support.microsoft.com/kb/310561
"
The 4-GB partition limit is imposed by the maximum number of clusters
and the largest cluster size supported by the FAT file system. In
Windows XP, FAT16 is limited to 64K clusters. Multiply the maximum
number of clusters (64k) by the maximum cluster size (64K), and the
result is 4GB. In addition to Windows XP, Microsoft Windows 2000 and
Microsoft Windows NT 4.0 also support FAT16 volumes up to 4GB in
size.

FAT16 volumes larger than 2GB are not accessible from computers
running Microsoft Windows Millennium Edition (Me), Windows 98, Windows
95, or MS-DOS. The size limit for FAT16 volumes in these operating
systems is 2 GB. In other words, to maintain compatibility with
Windows Me, Windows 98, Windows 95, or MS-DOS, a volume cannot be
larger than 2 GB. For additional information about FAT16 drive and
partition size limits in Windows Me, Windows 98, Windows 95, and MS-
DOS, click the article numbers below to view the article in the
Microsoft Knowledge Base:
"
So maybe in that list
"FAT16 volumes larger than 2GB are not accessible from computers
running ...."
One could add that not just Win9X, but BIOSs, or some BIOSs, do not
support it either.


On another related note- I seem to recall something like, from a LUA
(i.e. non administrative) account, you cannot read FAT32. But that is
not that relevant.

I guess the way to analyse some of these things is to write a program
to format disks! Or read FAT perhaps! I know scott mueller wrote
something analysing FAT16/32 in his UGRP book. And the starman website
has stuff.



Keep in mind that I use CF-IDE mostly for installation or
utilities, not running the OS (though i have done so in the
past). For (windows/etc) OS the CF card can be rather slow
unless you're using a fairly modern CF3.0 spec'd card and
the IDE adapter supports DMA. This is important to get it
out of PIO mode which limits it to about 6MB/s.

Note that some cards may occasionally be listed as only "CF
spec" or similar but they dont' come out and say which
version of the spec. You'd want CF3 or CF4 spec for fast
cards with this support. On the other hand if you just want
to get the job done as cheaply as possible, these days an
older PIO mode 2GB card can be had for under $15 and a
cheapie eBay CF-IDE adapter for about $3 + S/H.

It is pretty great just how low power consumption can be
using a CF card. I have a NAS enclosure on my desk that I'm
playing around with, which can also webserve and do P2P. I
temporarily put a CF card in it and it now consumes about
3.8W booting, 2.6W idle. It'd take more than that just to
power the hard drive.


what is a make/model of a good NAS enclosure for CF cards?


You mention slowness of CF I , but I saw a CF I card that did 133x
(20MB/s). Which is prob about the same as the newer type IIIs ?

for example
make- lexar , type I / type 1
make - Kingston, also CF 1, 4GB 133x
another that comes up is called Eagletec @ 150x. There seem to be
loads.

So that is fast, right? No need [for me] to bother with CF III
whatever advantage that has?


slightly OT note- i would probably be avoiding "microdrive" ones, they
prob make a noise. Good primer on compact flash cards - (I include a
bit of text from it so people can get it from the google cache if it
goes down) (archive.org is another option)
http://www.bobatkins.com/photography/digital/compact_flash_memory_cards.html
Compact Flash, SD and SDHC Memory Cards
"A common question from new digital camera owners is "which memory
card should I buy". The answer depends ......."
 
Interesting, I just checked, I do not have that problem.. (and my BIOS
- phoenix BIOS - does have an option for USB-HDD, and no RMD-Floppy
option). I figured my MBRD just did not support it.
But
Turns out it is fine,, same as my other very different machine. I do
not know why it did not boot off USB "last time"(I had only tried it
on one day, must have done something wrong that day).

BTW, OT, The VIA EPIA it seems had 2 processor options. C3 and EDEN.
C3 was faster but had a fan. I chose EDEN, which was fanless. Anyhow,
back onto the USB thing.


My C3 had a dinky heatsink w/fan, but I put a large passive
heatsink on it (after marking and drilling holes in it for
the proprietary through-board mounting these soldered-on
processors may need). It feels hot, but runs stable. Just
for the heck of it I put a duct into the PSU intake, it
wasn't hot enough that a lot of thought had to go into it,
just moving a slight bit more air past the heatsink
satisfied me. It was mostly to counter potential lockup
situations, in windows with ACPI HALT idling in effect the
heatsink was cool.


I did run into a problem booting USB, which I have isolated somewhat.

ntoe- I have not retested this.. But I am fairly sure I did not slip
up in these tests.

HPUSBFW.EXE (the famous program by HP, for formatting a usb key), has
an option to either format as FAT32, or instead, to format as what it
calls "FAT". )

(I know that at one time, prior to FAT32. You had FAT16 and FAT. FAT
was considered to be FAT12. But nowadays, you have FAT32, FAT16, and
FAT12. But FAT12 is not mentioned much, and FAT tends to refer to
FAT16).

Windows does not say whether by FAT, it means FAT12 or FAT16.
So looking at a USB key, one cannot see that way with Windows which it
is.


Unless you're talking about some tiny ancient flash drive,
it has to be referring to FAT16.

However.. FAT16 has a 2GB limit
16 bits for addresses, some size per address. (2^16 * x = 2GB ) x
happens to equal 32K (2^5=32K). But it is easier to remember the 2^16
and the 2GB !

FAT12 has a 2MB limit (1.44MB when formatted.)
2^12 * 512K = 2MB
FAT12 is used for floppy disks.

I noticed that HPUSBFW.EXE when told to format as FAT, was formatting
disks > 2GB as FAT16, and they were still > 2GB in available
capacity.


Hmm, I don't know if I'd ever tried to do that, I suspect
any over 2GB in size I automatically chose FAT32.

And those USB keys, > 2GB , formatted as what HPUSBFW.EXE called FAT,
do not boot. (they do view in windows xp though, but that is
irrelevant)

Whereas USB Keys formatted by HPUSBFW.EXE as FAT32, do boot.
And those USB keys < 2GB, boot, even if formatted as what HPUSBFW.EXE
calls FAT - which is no doubt FAT16. Do boot.

I find there are quite a few boards that won't boot anything
formatted to FAT32, they need FAT16 to recognize the
filesystem. This may be changing as motherboard bios become
more aware of the contemporary larger flash disk sizes which
require FAT32 if it would be a single partition.


The ones that fail/"do not boot", crash both my very different
computers, at the point in the BIOS, where it says Verifying DMI pool
data

One program that does display whether FAT16 or FAT12 is FDISK.. When I
booted off a USB key that booted. (a < 2GB USB key, formatted as
FAT16). FDISK saw it - as DOS does. And it said FAT16. So that
verifies that when HPUSBFW.EXE says FAT, it means FAT16. But it is
some mangled FAT16 when the drive is > 2GB.

Or perhaps not mangled.. but some Windows limit (and perhaps limit
from some or all BIOSs) on the "cluster size" with FAT16
Windows limit is not that relevant, but as a related note
and also, note that the USB keys I tried > 2GB, were 4GB
http://support.microsoft.com/kb/310561
"
The 4-GB partition limit is imposed by the maximum number of clusters
and the largest cluster size supported by the FAT file system. In
Windows XP, FAT16 is limited to 64K clusters. Multiply the maximum
number of clusters (64k) by the maximum cluster size (64K), and the
result is 4GB. In addition to Windows XP, Microsoft Windows 2000 and
Microsoft Windows NT 4.0 also support FAT16 volumes up to 4GB in
size.

Ok, but I dont' know that this has much to do with the
problem because the HP tool should be directly writing and
when in bios determining boot devices, windows doesn't have
anything more to do with what a bios can recognize.

However, it could explain windows having a problem accessing
it.


FAT16 volumes larger than 2GB are not accessible from computers
running Microsoft Windows Millennium Edition (Me), Windows 98, Windows
95, or MS-DOS. The size limit for FAT16 volumes in these operating
systems is 2 GB. In other words, to maintain compatibility with
Windows Me, Windows 98, Windows 95, or MS-DOS, a volume cannot be
larger than 2 GB. For additional information about FAT16 drive and
partition size limits in Windows Me, Windows 98, Windows 95, and MS-
DOS, click the article numbers below to view the article in the
Microsoft Knowledge Base:
"
So maybe in that list
"FAT16 volumes larger than 2GB are not accessible from computers
running ...."
One could add that not just Win9X, but BIOSs, or some BIOSs, do not
support it either.


On another related note- I seem to recall something like, from a LUA
(i.e. non administrative) account, you cannot read FAT32. But that is
not that relevant.

I guess the way to analyse some of these things is to write a program
to format disks! Or read FAT perhaps! I know scott mueller wrote
something analysing FAT16/32 in his UGRP book. And the starman website
has stuff.

What exactly is your goal again?
It's not as though we'd really want access to a large
capacity over USB2, it's too slow to be put to that kind of
use, relatively speaking. 2GB limit is not much of a
problem, _yet_, IMO.


what is a make/model of a good NAS enclosure for CF cards?


It isn't an enclosure for CF cards, it's just a regular NAS
external enclosure with a CF-IDE adapter.
You mention slowness of CF I , but I saw a CF I card that did 133x
(20MB/s). Which is prob about the same as the newer type IIIs ?

20MB/s is slow.

It's even slower when MLC chips with lower write speed.
What you are you calling a "type IIIs"? Compact Flash spec
before 3.0, caused it to operate in PIO mode when used in
ATA mode, running at about 6MB/s, not 20MB/s.

So you have three options:

1) Very compatible PIO mode at 6MB/s
2) Very quirky and only moderately fast and high overhead
USB2 interface.

3) The best option - DMA, ATA66 or faster mode using CF3 or
4 spec'd cards on PATA controllers. While USB2 can seem
ok in larger sustained transfers, it is quite a bit slower
at more typical file access patterns running an OS.
for example
make- lexar , type I / type 1
make - Kingston, also CF 1, 4GB 133x

What are you calling CF1? You mean the height of the card?
Forget about form-factor, isn't applicable. CF3 or 4 spec
is not like "Type 1" or "Type 2", those are just physical
dimensions.


another that comes up is called Eagletec @ 150x. There seem to be
loads.

So that is fast, right? No need [for me] to bother with CF III
whatever advantage that has?

You have the options I mentioned above, quirky USB, slow PIO
6MB/s and high CPU utilization with all CF specs below 3.0,
or 3.0 or 4 being the only ones with relatively good
performance, (which was why I wrote it?).

Pick, cheap or fast.
 
.....................................

I find there are quite a few boards that won't boot anything
formatted to FAT32, they need FAT16 to recognize the
filesystem. This may be changing as motherboard bios become
more aware of the contemporary larger flash disk sizes which
require FAT32 if it would be a single partition.

I have an unusal situation, for me. If I used the boot sector of IBM DOS 6.3
& created the needed files in an usb flashdrive, the computer won't boot from
the flashdrive. BUT if I used a diskette formated by winxp as a "starter" disk
to create the boot flashdrive (same flashdrive as previous), the the computer
would bootup.

A disketter with IBM DOS will boot as a floppy tho! Guess boot sectors contain
more info now?
.................................................
 
I have an unusal situation, for me. If I used the boot sector of IBM DOS 6.3
& created the needed files in an usb flashdrive, the computer won't boot from
the flashdrive. BUT if I used a diskette formated by winxp as a "starter" disk
to create the boot flashdrive (same flashdrive as previous), the the computer
would bootup.

A disketter with IBM DOS will boot as a floppy tho! Guess boot sectors contain
more info now?
.................................................

http://en.wikipedia.org/wiki/Master_boot_record
 
Back
Top