On Thu, 03 Jun 2021 01:44:01 +0200, Bryan Kilgallin wrote:
> "The command didn't complete.", or "The command hung.".
No, hang means stop in the middle, so typically it would not then complete.
> "or it might complete unsuccessfully (disk is not usable)."
> "The command failed."
Well, you can
On Wed, Jun 2, 2021 at 7:45 PM Bryan Kilgallin wrote:
>
> > Something like formatting a disk might not complete (eg hardware
> > error)
> "The command didn't complete.", or "The command hung.".
>
> "or it might complete unsuccessfully (disk is not usable)."
> "The command failed."
If the command
Tomas:
Something like formatting a disk might not complete (eg hardware
error)
"The command didn't complete.", or "The command hung.".
"or it might complete unsuccessfully (disk is not usable)."
"The command failed."
--
members.iinet.net.au/~kilgallin/
(This is probably not the right forum for this, but whatever.)
On Thu, 03 Jun 2021 00:22:03 +0200, Bryan Kilgallin wrote:
> I read "The command completed successfully." This seems to me
> programmer-speak, and verbose. Why not simplify that to "The command
> succeeded."?
Because it might be a
I read "The command completed successfully." This seems to me
programmer-speak, and verbose. Why not simplify that to "The command
succeeded."?
--
members.iinet.net.au/~kilgallin/
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
Thanks for the info. I will test more combinations and get back. Yes, I
have seen the reboot commands, so it should be fine. I try restart after
leaving the app, simply from command line.
None of the apps provide any docs that they would require OAKCDROM. I guess
it will work with other Windows
Hi Lukas,
Glad to hear that you found a solution for copy protected games!
I assume none explicitly demanded OAKCDROM? What do the docs say?
The question will be what exactly OAKCDROM does better than UDVD2,
regarding copy protected games. Not easy to say with closed source.
But good to know
Hi, I got it fixed in FreeDOS! Thanks for explaining the level 1 and level
2 drivers. It helped me.
The floppy disc of Windows 98 contains about 4 different CD-ROM drivers. I
went with the first oneL OAKCDROM.SYS
These are the results:
1) UDVD2 + SHSUCDX = NOT WORKING
2) OAKCDROM + SHSUCDX =
Hi! Forwarding a message from Lukas, accidentally sent only to me.
To already reply to his points: It is a common problem that 486 can
not boot from CD-ROM, but we provide a boot floppy image with the
right drivers to boot your 486 and then start our CD installer :-)
Note that our installer
Hi Jerome,
if FDIMPLES is specifically used in advanced mode, where
more data has to be processed, I would suggest to consider
automatically enabling support for XMS when XMS is found.
Do you say that the amount of required RAM does not depend on
the number of packages, but on the size of the
Hi Eric,
> On Jun 2, 2021, at 6:33 AM, Eric Auer wrote:
>
>
> Hi Jerome,
>
> thanks for the explanation, but are we talking about DOS
> RAM (at most 640 kB) here? Or EMS, XMS, protected mode?
FDIMPLES and FDINST are both made for 8086. FDIMPLES is limited to only using
low memory (640k). I
Hello Tom,
> On Jun 2, 2021, at 6:35 AM, tom ehlert wrote:
>
> Hallo Herr Jerome Shidel,
>
> am Mittwoch, 2. Juni 2021 um 02:39 schrieben Sie:
>
>
>
On Jun 1, 2021, at 11:10 AM, Eric Auer wrote:
>>>
>>>
>>> Hi Lukas,
>>> […]
>>>
said it is memory issue and solved also by
Hallo Herr Jerome Shidel,
am Mittwoch, 2. Juni 2021 um 02:39 schrieben Sie:
>> On Jun 1, 2021, at 11:10 AM, Eric Auer wrote:
>>
>>
>> Hi Lukas,
>> […]
>>
>>> said it is memory issue and solved also by installing FreeDOS on hard drive
>>> in Pentium machine. That's how I did it as well and
Hi Jerome,
thanks for the explanation, but are we talking about DOS
RAM (at most 640 kB) here? Or EMS, XMS, protected mode?
In FDIMPLES, FDINST of FDNPKG, and other involved apps?
How much RAM do you recommend to be free? Could FDIMPLES
shrink before calling FDINST and grow back when it exits?
> You see how many subscribers and views Phil has.
it's always kind to not only mention 'Phil', but be more specific like
"go to Youtube.com, search FreeDOS 1.2 Review - Can it replace MS DOS
for retro gaming?"
or even give the link directly. https://www.youtube.com/watch?v=zGmCVeAKR4w
> A lot of games I tried with JEMM386/JEMMEX had some really jarring
> issues. They varied from the game gracefully crashing to outright raping
> my ears or gradually eroding FAT away. FreeDOS' own FAT repair tools
> couldn't help me. Only nuking everything and re-installing and
>
On 01/06/2021 23:55, Lukas Satin wrote:
The driver VIDECDD is not working at all. It will not find my CD-ROM
drive. Perhaps because 486 bios cannot find the CDROM. But driver such
as MSCDEX or SHSUCDX will find the drive.
Hi Lukas, MSCDEX/SHSUCDX are not really drivers, they are only a
17 matches
Mail list logo
