I am setting up a LINUX, openSUSE 10.2, with FreeDOS under qemu so that it
can be accessed remotely for data updates through an old Clipper program.
So my first try was to just setup a client to log onto LINUX box and try to
boot a qemu image of FreeDOS. Well it booted but the screen did not show
I'm sorry guys and girls, but I've been working with FreeDOS for quite
some time and I don't understand why on earth some of you have such
problems, getting FreeDOS to work :-/
I've got FreeDOS working on a dedicated machine, without a glitch!
In my point of view there's absolutely *nothing* wr
Hi all, please update your dosfsck to
www.coli.uni-saarland.de/~eric/stuff/soft/by-others/dosdosfsck-2.11c.zip
which now has progress in for for the -t option
which can be enabled by the -v option. If you
use -t without -v, is shows a hint "use -v" :-).
Background: The -t option of dosfsck ta
Hi, Eric
12 minutes to do a 2045 Mb drive partition on one of my
older Celeron 400Mhz systems -- not bad! Counter moves
two-three times a second.
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log fi
Hello Eric,
you wrote:
> Still it is better to have the right pointer type. Not sure what the
> bug is, but pointing to the wrong kind of object cannot be the solution.
Of course. But you know the Edit's code much better than I know it...
--
Oleg O. Chukaev
Hi, Eric
Your 2.11c version is great! It's just what that utility
needed to prevent confusion when using very large hard
disks. I let 2.11b run overnight and it finished okay. The
counter, at least, lets one know that it will take a l-o-n-g
time to finish!
Interesting twist on install routine:
Hello Eric,
you wrote:
> of if. Makes the code more readable and makes it easy to connect
IMHO Edit's code is a good candidate for winning on the IOCCC ;-)
> I guess you mean DN for next and UP for prev.
Yes, you're right.
>> I removed `static' keyword from {Next,Prev}Focus definitions and
>>
Roughbert Strong wrote:
> stick, booting starts OK but soon stops with "media
What happens exactly?
> test failure check cable". I've seen this error
"Check cable" probably comes from your NIC (PXE), because BIOS couldn't
boot the stick.
Robert Riebisch
--
BTTR Software
http://www.bttr-softwa