I am writing a TSR, and having trouble getting it to work with FreeDOS. It
installs just fine in MSDOS, also also installs just fine from a FreeDOS
command prompt. But, when I try to install it using an INSTALL= or
INSTALLHIGH= from CONFIG.SYS, the machine hangs. The hang occurs right
after
I'm attaching a file that has a simple TSR with the problem (TESTFAIL.COM),
as well as one that doesn't (TESTPASS.COM). I'm also including the source
code (TEST.A36, in A386 format), as well as the KERNEL.SYS CONFIG.SYS I
used to test with. The only difference between TESTFAIL TESTPASS is the
Thanks, Christian!
When I first came across this problem, it seemed like maybe INSTALL= was
using memory without an appropriate MCB, though from just perusing the code
it looked like it was using INT 21.48 to allocate the memory. I had
actually tried allocating an extra 64k segment at the top
The advantage of a write-delay cache is that that the writing can be
done when the system is idle (a simple form of multi-tasking).
That counts as advanced cache with a lot of code and can go as far as a
sort of ramdisk which syncs
back to the harddisk slowly but steadily when the
I use NTFS under Windows. Mark Russinovitch offered a freeware NTFS
*reader* for DOS through his
old Sysinternals site, and a payware driver that could also *write* to
NTFS from DOS through the sister
Winternals site. (It was intended for rescue operations on NTFS
filesystems from DOS.)
Eric Auer-3 wrote:
...
I find it a very good idea in USB drivers to support the ASPI API so other
drivers and client apps can use
that to access the drives in question :-)
I disagree. ASPI and INT 13h are essentially competitive technologies, not
complementary. If a disk can be
Mark Brown-27 wrote:
you *could* try USBASPI.SYS /V /W
followed by DI1000DD.SYS
( works for me )
In my opinion, this is applying a band-aid to a problem that actually
requires drastic surgery. USBASPI.SYS + DI1000DD.SYS may in fact work in
certain situations. But, it is not a
I personally would like to see modern DOS applications (the few that are
still being developed) support the multimedia keys, power management keys,
and scroll wheels on keyboards and mice. Modern (USB) keyboards and mice
almost always have them, but DOS applications, even modern ones, almost
Bertho Grandpied wrote:
Therefore my first interrogation is, what set of device header attributes
- and associated functions, including IOCTL codes - must be present /at a
minimum/ for letting DOS access the disk properly ?
- For a tentative and probably naive self answer, could I get away
Nanosecond resolution is a little tough, but microsecond is pretty easy just
using the PIT. Is microsecond good enough for your purposes?
--
View this message in context:
http://old.nabble.com/hardware-timer-QueryPerformanceCounter-tp33536190p33544671.html
Sent from the FreeDOS - User mailing
FWIW, I had problems with my computers also. The original DSL modem I had
(provided by the phone company) worked fine, but it eventually went belly
up. I bought a new one (made by ActionTec), but for some unknown reason DOS
WATTCP doesn't like the DHCP server provided by the new modem. In
Some DOS *apps* cared and choked on it, so I wrote Korn shell alias
wrappers to reset the option
delimiter char to / before running them, and set it back to - when they
exited.
Like I said, this is why it won't work in the _general_ case. There are
situations and programs where it can work,
If you could boot up in only a few seconds, would you turn things off when
you weren't using them (not necessarily servers, but clients)?
--
View this message in context:
http://old.nabble.com/Long-term-survival-of-FreeDOS-tp33661875p33684868.html
Sent from the FreeDOS - User mailing list
Jack-181 wrote:
I will NOT cache a drive which cannot tell me when its media has changed,
and I REFUSE to add all of the
logic in UIDE that Eric notes the DOS kernel contains, to find out if a
media-change has occurred using other methods!
It's not impossible to cache floppies, Jack. You
Marcos:
So where exactly is the file server that's storing the data file(s) in this
scenario? Is it on the doctor's PC, assistant's PC, or some other location?
--
View this message in context:
http://old.nabble.com/Networking-tp34020890p34021413.html
Sent from the FreeDOS - User mailing list
You could try the Text Mode utility from Jason Hood, available here:
http://adoxa.3eeweb.com/
--
View this message in context:
http://old.nabble.com/Video-modes-tp34636525p34649342.html
Sent from the FreeDOS - User mailing list archive at Nabble.com.
16 matches
Mail list logo
