Hey,
if not exist mydir/nul md mydir
Doesn't work on XP (I think?), but that's the typical DOS way.
This kept bothering me for some reason, so I checked now.
It appears to work just fine on MSW NT command lines, executing the
command after if not exist dir\nul if and only if that directory
Jack,
[others: this is a bit long/technical, the summary is that it
is both easy and safe to use shallow drive power management.]
The problem is WHERE does UIDE or any other driver wait for
a sleeping, i.e. stand-by hard disk to awaken again?? The
ATA specs do not make this clear. Can
Hi Cordata,
All this talk about UIDE prompted me to investigate this tool. It
looks interesting. How does the caching work for disk writes? I
assume that when the cache is full the next sector read in will cause
the oldest sector to be written out?
Neither UIDE nor lbacache nor cdrcache
Hi Christian,
if not exist mydir/nul md mydir
Doesn't work on XP (I think?), but that's the typical DOS way.
This kept bothering me for some reason, so I checked now.
It appears to work just fine on MSW NT command lines, executing the
command after if not exist dir\nul if and only if
Hi Eric,
As far as I remember, the DOS findfirst API is supposed to find
character devices (such as NUL) in any (existing) directory, so
this would depend more on DOS than on COMMAND, but I am not sure.
Without any further investigation, I'd say that's part of it. However,
aside from the
All this talk about UIDE prompted me to investigate this tool.
It looks interesting. How does the caching work for disk writes?
UIDE uses Write Through caching, meaning all output data is written
to disk immediately. For SATA/IDE disks handled internally by UIDE,
if data fits in one cache
Eric,
I read through and understood all your comments about hard-disk
power management, etc.
My problem is: I am not-interested in being the one who does
power management. If DOS or the BIOS wants to save power thru
putting disks into stand-by mode, let them do it. UIDE is a
disk I-O
Jack,
I read through and understood all your comments about hard-disk
power management, etc.
My problem is: I am not-interested in being the one who does
power management. If DOS or the BIOS wants to save power thru
putting disks into stand-by mode, let them do it...
There is not much
Eric,
... My problem is: I am not-interested in being the one who
does power management. If DOS or the BIOS wants to save power
thru putting disks into stand-by mode, let them do it...
There is not much to do there, as you only tell the disk once
and then the disk itself does the rest.
http://johnson.tmfc.net/dos/index.html
--
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to
Jack,
There is not much to do there, as you only tell the disk once
and then the disk itself does the rest.
Amen!, so let the user handle this thru the BIOS setup routines
and let the BIOS tell the disk what to do during system boot!
BIOS vendors have many more programmers than just me by
That is a very good link ... Thank You.
Regards,
Ferry
--- On Sat, 5/14/11, Alvin P. Schmitt schmitt.al...@gmail.com wrote:
From: Alvin P. Schmitt schmitt.al...@gmail.com
Subject: [Freedos-user] Interesting Chinese (english) DOS stuff plus system
programmer book for dos.
To:
Eric,
I have not yet seen a desktop BIOS which implements this, alas [disk
spin-down timeouts, etc.]. I do have an adware DOS tool for it,
showing a splash screen for a BBS or similar when you run it and of
course bigger than needed, but free.
Desktop BIOS routines are usually
13 matches
Mail list logo