On Sat, 14 Jan 2012 Michael B. Brutman wrote :
As far as 4K blocks go, I wouldn't worry about it too much. 512 byte
sectors will be supported either natively or by emulation in the drive
itself for a long time to come - at least 5 to 10 years. Too many
existing systems depend on a 512
Op 15-1-2012 3:56, dos386 schreef:
[Freedos-kernel] FreeDOS 1.1 released
COOL :-)
thanks, worked hard for it :)
http://jafile.com/uploads/dos386/freeds11.png
I like your style of coming up with screenshots, it clarifies issues
quite nicely. I wish VMware's video feature would use standard
Eric Auer e.a...@jpberlin.de wrote :
Interestingly, even 3 TB disks are still sold with 512 byte sectors.
Conversely, even 1 TB USB disks are already sold with 2048 byte sectors ;=)
(...snipping much...)
By the way - a DRIVER could interface with any disk with
any sector size and then just
Op 14-1-2012 23:23, Eric Auer schreef:
Talking about new ways of booting, it would be very interesting to
have a CD / DVD / BD boot loader for DOS. However, after you loaded
the kernel, you still need some initrd from which you can load a
CD/... driver pair like UIDE + SHSUCDX or ...CDROM +
Bertho,
I spoke from the point of view of the device (the hard drive) - if the
hardware that the device is attached to chooses not to expose all of the
options that the device supports, there is little the device can do
about that. In the case of your external storage somebody made a design
FWIW:
In my USB disk driver (USBDRIVE), here's what I've done.
USBDRIVE does not try to virtualize the sector sizes as others are suggesting
here as a possibility -- I figure doing that has the potential to cause as many
problems as the alternative (using defective utilities/programs that are
Hi Bret,
USBDRIVE does not try to virtualize the sector sizes as others are
suggesting here as a possibility -- I figure doing that has the
potential to cause as many problems as the alternative...
Maybe you could make that configurable, so people can experiment
with virtual 512 byte sectors
In reply to : Michael B. Brutman mbbrut...@brutman.com
Michael,
So the bottom line is that DOS will probably work just fine
when
natively attached to storage devices, and that will work
for a long
time. Appliance storage devices are going to break
that if they can't
emulate 512 byte
In response to : Bret Johnson
Subj : MSDOS - increasing max sector size
...
Likewise, it will ignore disks with sector sizes larger
than what DOS says it can handle (this particular detail is
part of the easily accessible DOS List of Lists). In
the source code for USBDRIVE (starting at line
New follow-up ! In response to : Bret Johnson
Subj : MSDOS - increasing max sector size
quoting myself (sorry!) :
According to Rudolf Loew, increasing maximum sector size in LoL of an
unpatched MSDOS will work up to 2048 byte sectors, not 4096 :( I have
not verified it for a fact.
Wow!
2012/1/15 dos386 dos...@gmail.com
would be nice to know how many people actually installed it
successfully on a __REAL__ PC ;-)
I did and did it successfully. Yes, it did hang on the commandx but not
mortally - for a while like some 2 minutes and then continued without
problems.
On a
2012/1/15 dos386 dos...@gmail.com
Other:
- CWSDPMI, VSM, DOSNTLFN, ... are in
- INFOPAD, 7-ZIP, UNTGZ, HX/HDPMI32, MPXPLAY, FASM, CC386, FREEBASIC,
ARACHNE, ... are NOT in ... what can you do with it when installed ?
As for the mpxplay copied it into /fdos/bin from the previous
USBDRIVE does not try to virtualize the sector sizes as others are
suggesting here as a possibility -- I figure doing that has the
potential to cause as many problems as the alternative...
Maybe you could make that configurable, so people can experiment
with virtual 512 byte sectors at their
Hi Bret,
maybe virtual 512 byte sectors are actually not that evil:
Imagine a NORMAL 4096 byte sector based FAT32 filesystem.
Each cluster and each FAT will be a multiple of 4096 byte
in size, as will be the boot and fsinfo sectors. In FAT32
the root directory is just any directory, so like all
Hi Bret,
Not Bret, but I'll provide answers to 2 of your points.
BPB CHS geometry differs - but does a disk with 4096 byte
sectors allow CHS based access at all? I hope it does not.
you can't preclude it, it may for compatibility sake (at the int 13h
interface).
(big big snipping)
By
Thanx all,
but as I said its impossible to figure out what driver is causing the problem,
the sequence doesn't seem to be logical to fix the problem.
it crashes AFTER the boot has finished.
I installed version 1,0 ( 0.87 beta ) with no problem.
tx
ralph
On Jan 15, 2012 6:04 PM, Ralph Deffke ralph_def...@yahoo.de wrote:
Thanx all,
but as I said its impossible to figure out what driver is causing the
problem, the sequence doesn't seem to be logical to fix the problem.
it crashes AFTER the boot has finished.
I installed version 1,0 ( 0.87
wish VMware's video feature would use standard codecs so
something could be posted to Youtube or
Please provide your movies in OGV or WebM files, not Loo-Tube.
- It fails to find any HD (see middle shot)
In the normal configurations or the dedication one?
Both, but in normal configurations
Please try to empty FDCONFIG.SYS and FDAUTO.BAT, and re-add USEFUL
things piece after piece ... and supply shot of the crash ... it
crashes AFTER the boot has finished is NOT very informative.
--
RSA(R) Conference 2012
maybe virtual 512 byte sectors are actually not that evil:
Imagine a NORMAL 4096 byte sector based FAT32 filesystem.
...
Actually they are, or at least potentially are, at least from a compatibility
perspective. In the case of USB, the SCSI protocol is normally used. The
sector size is not
20 matches
Mail list logo
