Hi Mercury and Jerome,
I typically do modify the times to reflect the version number. Of
course that's not necessary by any means, but it's a habit I started
doing as a quick and easy contingency to help me in the event of files
becoming crossed, e.g. if I were to accidentally drop files into
I typically do modify the times to reflect the version number. Of course that's
not necessary by any means, but it's a habit I started doing as a quick and
easy contingency to help me in the event of files becoming crossed, e.g. if I
were to accidentally drop files into the wrong version folder
Hi Jim,
> On Oct 1, 2023, at 7:05 PM, Jim Hall via Freedos-user
> wrote:
>
> Eric wrote:
>> You can also find updates for JEMM and HIMEMX on Japheth's GitHub "Baron von
>> Riedesel", even his HIMEMSX to use more than 4 GB RAM :-)
>
> Mercury Thirteen wrote:
> [..]
>> Looks like I fell behind
Eric wrote:
> You can also find updates for JEMM and HIMEMX on Japheth's GitHub "Baron von
> Riedesel", even his HIMEMSX to use more than 4 GB RAM :-)
Mercury Thirteen wrote:
[..]
> Looks like I fell behind on keeping up with all of Japheth's updates! The
> downloads section at MercuryCoding.com
From: Tony Richardson
--===2988458840748287315==
Content-Type: multipart/alternative; boundary=047d7bb04c5cfc34b905454d4114
--047d7bb04c5cfc34b905454d4114
Content-Type: text/plain; charset=UTF-8
Although the standard installer gave me this same error, the legacy
installer worked fin
From: Rugxulo
Hi,
On Sun, Jan 1, 2017 at 4:43 PM, wrote:
>
> I tried to boot FreeDOS 1.2 on my 2005 PC, specs:
>
> It is the FD12CD.ISO image, booted from CD-R. I chose "Install" and used
> F8 to diagnose the problem.
>
> DEVICE=\FDSetup\BIN\HIMEMX.EXE stalls the system. It infinitely repeads:
From: Jerome Shidel
> On Jan 4, 2017, at 9:16 AM, Tony Richardson
wrote:
>
> I am having exactly the same problem (Invalid Opcode at HIMEMX line) with a
laptop from the same era. FreeDOS 1.1 installed without problems. I was using
the 1.2 standard CD. I plan to try the 1.2 legacy CD tonight
From: Tony Richardson
--===2574402294996377512==
Content-Type: multipart/alternative; boundary=001a1146d9ce9f04e10545456e46
--001a1146d9ce9f04e10545456e46
Content-Type: text/plain; charset=UTF-8
I am having exactly the same problem (Invalid Opcode at HIMEMX line) with a
laptop from
> There is a bugfix release available for HimemX at
>
> http://www.japheth.de/Himem331.zip
>
sorry, the link actually is
http://www.japheth.de/Download/Himem331.zip
-
This SF.net email is sponsored by: Splunk Inc.
Still gr
Hello,
There is a bugfix release available for HimemX at
http://www.japheth.de/Himem331.zip
The first bug caused v3.30 to fail on cpus < pentium when running in
real-mode, the latter gave "unexpected results" when running on MS-DOS 6.x
(and most likely 5.x, 4.x and 3.x as well).
In case you w
10 matches
Mail list logo
