Re: [Freedos-user] retro gamer review of FreeDOS 1.3

[Joao Silva]

Hello.

I agree with you, a VM isn't a viable solution for testing.
I'm in favor  of using real hardware.

My floppies games i tested on VM run well on my IBM 286 (real machine).

The downloaded games had options that my don't have.

I do have a PII and PIII that i'll try freedos, but no anytime soon... for
now i'l stick to emulation.


On Tue, Mar 8, 2022 at 10:35 PM Eric Auer  wrote:

>
> Hi!
>
> Please stay relaxed about this topic, it would be great to know WHY
> certain games do not work well in FreeDOS, so we can improve it :-)
>
> Of course you can also run those games in various emulators or using
> other versions of DOS. This may even provide insights regarding how
> to configure FreeDOS, another DOS, or some emulator the best way for
> the game in question. So I would not want to exclude talking about
> other DOS or emulators, but my goal would still be finding out how
> to make all games work in FreeDOS - if necessary, by pointing out
> bugs in FreeDOS.
>
> That said, in case you have Linux (not sure about the porting state
> of DOSEMU2 to Windows or other OS), could you test the games here
> with DOSEMU2 and FDPP? The FDPP module of DOSEMU2 is a port of the
> FreeDOS kernel to the Linux side of the emulator, with some glue on
> the DOS side, so it is a bit hard to compare to classic FreeDOS, but
> it has lots of patches which may have already solved the game issues
> so it would be cool to know how well the tricky games run with that.
>
> FDPP is the default "DOS" for DOSEMU2, but you can still use DOSEMU2
> like a more generic VM or emulator and install classic FreeDOS on it,
> either in a diskimage drive or in a "Linux directory posing as a DOS
> drive". The latter requires loading some special DOS drivers to gain
> write access after boot. In DOSEMU (non-2), some magic was built-in
> to provide more services without manually loading DOS drivers, so that
> just had a normal FreeDOS kernel as default guest operating system.
>
> Regarding the option of using MS DOS 6.22: That one has not been
> updated for 30 years and it fails to understand things such as
> disks beyond 8 GB (or even 0.5 GB) in size, modern amounts of RAM,
> FAT32 partitions, and so on. Plus of course it is neither free nor
> open source. So FreeDOS has many nice features which MS DOS 6.22 is
> missing, but of course games from 30 years ago have only been tested
> by their developers with DOS from 30 years ago, so there is always a
> risk that we broke compatibility in how we implement exotic APIs. As
> you mention, Win9x DOS 7.x is an option for some - but even that is
> neither free nor open source and there is no ongoing development, so
> nobody who can help you to improve it if anything is not working well
> for example on any "too modern" hardware.
>
> > Alas, FAT-32 MS-DOS introduces issues of its own with other games.
> > Starflight 1 and 2 have problems on these installed, and Tsunami Media
> > games (Man Enough, Return to Ringworld, just to name a few) refuse to run
> > completely. All these games Run flawlessly on FreeDOS.
>
> That surprises me, as a default install of FreeDOS has FAT32 enabled.
> Do those games just refuse to run when the game itself is on a FAT32
> drive? Or do they actually care about whether DOS knows about FAT32?
>
> > So you downloaded some of those games and they ran but had speed issues
> and
> > exited with error code. Then you tried your Floppy versions and you
> report
> > black screen with no errors (same as others and me included had
> reported).
> > And you tested all this between 1.3rc4 and 1.3 live on a VM.
>
> That sounds like a lot of effort in testing, but if all tests were on
> virtual machines, the problem can simply be caused by the VM itself,
> for example not properly emulating DOS age VGA graphics or SB16 etc.?
>
> Regards, Eric
>
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] retro gamer review of FreeDOS 1.3

[Eric Auer]

Hi!

Please stay relaxed about this topic, it would be great to know WHY
certain games do not work well in FreeDOS, so we can improve it :-)

Of course you can also run those games in various emulators or using
other versions of DOS. This may even provide insights regarding how
to configure FreeDOS, another DOS, or some emulator the best way for
the game in question. So I would not want to exclude talking about
other DOS or emulators, but my goal would still be finding out how
to make all games work in FreeDOS - if necessary, by pointing out
bugs in FreeDOS.

That said, in case you have Linux (not sure about the porting state
of DOSEMU2 to Windows or other OS), could you test the games here
with DOSEMU2 and FDPP? The FDPP module of DOSEMU2 is a port of the
FreeDOS kernel to the Linux side of the emulator, with some glue on
the DOS side, so it is a bit hard to compare to classic FreeDOS, but
it has lots of patches which may have already solved the game issues
so it would be cool to know how well the tricky games run with that.

FDPP is the default "DOS" for DOSEMU2, but you can still use DOSEMU2
like a more generic VM or emulator and install classic FreeDOS on it,
either in a diskimage drive or in a "Linux directory posing as a DOS
drive". The latter requires loading some special DOS drivers to gain
write access after boot. In DOSEMU (non-2), some magic was built-in
to provide more services without manually loading DOS drivers, so that
just had a normal FreeDOS kernel as default guest operating system.

Regarding the option of using MS DOS 6.22: That one has not been
updated for 30 years and it fails to understand things such as
disks beyond 8 GB (or even 0.5 GB) in size, modern amounts of RAM,
FAT32 partitions, and so on. Plus of course it is neither free nor
open source. So FreeDOS has many nice features which MS DOS 6.22 is
missing, but of course games from 30 years ago have only been tested
by their developers with DOS from 30 years ago, so there is always a
risk that we broke compatibility in how we implement exotic APIs. As
you mention, Win9x DOS 7.x is an option for some - but even that is
neither free nor open source and there is no ongoing development, so
nobody who can help you to improve it if anything is not working well
for example on any "too modern" hardware.


Alas, FAT-32 MS-DOS introduces issues of its own with other games.
Starflight 1 and 2 have problems on these installed, and Tsunami Media
games (Man Enough, Return to Ringworld, just to name a few) refuse to run
completely. All these games Run flawlessly on FreeDOS.


That surprises me, as a default install of FreeDOS has FAT32 enabled.
Do those games just refuse to run when the game itself is on a FAT32
drive? Or do they actually care about whether DOS knows about FAT32?


So you downloaded some of those games and they ran but had speed issues and
exited with error code. Then you tried your Floppy versions and you report
black screen with no errors (same as others and me included had reported).
And you tested all this between 1.3rc4 and 1.3 live on a VM.


That sounds like a lot of effort in testing, but if all tests were on
virtual machines, the problem can simply be caused by the VM itself,
for example not properly emulating DOS age VGA graphics or SB16 etc.?

Regards, Eric



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] retro gamer review of FreeDOS 1.3

[Joao Silva]

I agree completely you there is no point in continuing this discussion... i
just use freedos to debug games memory and jump back to emulation!

On Tue, Mar 8, 2022 at 9:56 PM Carlos Teixeira 
wrote:

> Why FreeDOS if i can use other MS (and others) versions of DOS? 6.22
> should be the best option but, for a special purpose all rounder DOS
> computer i'm using (because i lack the space to use several builds) FAT16B
> is too limiting. With this in mind i have 2 options: strip DOS outta
> Windows 98SE (or just use the CDU 7.1) or FreeDOS. Both allow FAT32.
>
> Alas, FAT-32 MS-DOS introduces issues of its own with other games.
> Starflight 1 and 2 have problems on these installed, and Tsunami Media
> games (Man Enough, Return to Ringworld, just to name a few) refuse to run
> completely. All these games Run flawlessly on FreeDOS. Considering i
> already use several FreeDOS included drivers (CTMouse, mkeyb, HIMEMX, again
> just to name a few) there's no reason why i and others can't aspire to use
> FreeDOS with better compatibility and usability than the old unmaimtened
> and closed source FAT32 DOS or even the older less feature packed 6.22.
>
>
> So you downloaded some of those games and they ran but had speed issues
> and exited with error code. Then you tried your Floppy versions and you
> report black screen with no errors (same as others and me included had
> reported).  And you tested all this between 1.3rc4 and 1.3 live on a VM.
> Oh... You know what? There's no point in continuing this discussion with
> you. The OP made a thread about a video a retro gamer made testing FreeDOS
> compatibility with some games on bare metal. This is just turning mind
> blowingly non sequitur between DOSBox and VMs so, seriously, let's just end
> this.
>
> A terça, 8/03/2022, 19:20, Joao Silva  escreveu:
>
>> First of all i'm not Dude if more Sir or Mr.
>> I don't know you and certainly i'm not your friend...
>>
>> Moving on... downloaded the games mentioned above and using my freedos
>> 1.3-RC4 i was able to run Test Drive 2 and Grand Prix and Cycles ran the
>> intro fast and exited with a error code.
>> Test Drive 2 played and exited with a error.
>>
>> I grabbed my floppies with the same games (except for cycles) they did
>> not run, got a black screen and no error output.
>> Runnnig on a VM Freedos 1.3-RC4 and 1.3 Live
>>
>> And the final question what do you want with Freedos if you have and quote
>> "
>> I also can use from CP/M-86 to all MS-DOS oficial releases to Windows 98
>> stripped FAT32 MS-DOS. PC-DOS, DR-DOS, whatever.
>>
>> "
>>
>> They should run games better than Freedos!
>>
>> On Mon, Mar 7, 2022 at 8:43 PM Carlos Teixeira 
>> wrote:
>>
>>> Dude... I do have the right hardware from an original IBM XT to a couple
>>> Turbo XT clones, to a Tandy 1000 SL that i had to mod for 220V, to a 286,
>>> 386, 486 and Pentium MMX.
>>>
>>> I also can use from CP/M-86 to all MS-DOS oficial releases to Windows 98
>>> stripped FAT32 MS-DOS. PC-DOS, DR-DOS, whatever. No point in discussing
>>> DOSBox. The point here is:
>>>
>>> FreeDOS and its ability to run DOS games. In the case of DSI games,
>>> there's something specific to the game engine that prevents those games
>>> from running, GP Circuit, The Cycles and Test Drive 2. I've had no chance
>>> yet but a good thing try might be running a debugger and checking if the
>>> code might be stuck in an infinite loop.
>>>
>>> Planet X3, for instance, despite being programmed for XT class machines
>>> that usually use MS-DOS 3.3, had a bug in which the game was stuck in an
>>> infinite loop while printing a string just before exiting to DOS. So i took
>>> a look into the code and what happened is that INT 29 might trash BX
>>> completely which was actually used to point to memory and fetch the
>>> characters for the string. BX gets completely trashed so the string never
>>> finished and just printed crap on the screen. An isolated problem on a
>>> specific version of DOS.
>>>
>>> This might be what is happening with the DSI games, or might be
>>> something entirely different, but the fact that every game that uses the
>>> same engine fails to run on FDOS makes it quite obvious that fixing just
>>> one of these games will probably fix the rest. This is what we should focus
>>> on.
>>>
>>> A segunda, 7/03/2022, 13:04, Joao Silva  escreveu:
>>>
 Hello!

 Not perfectly... for that you need the right hardware for the game to
 run, ms-dos 6.22 or pc-dos 7.0/7.1 and i'm assuming that you don't have
 either conditions.

 So dosbox will run most games, you can check the compatibility list
 https://www.dosbox.com/comp_list.php?letter=a  and fine tune the cpu
 speed on dosbox.

 You  can also check dosbox-x with more features.

 You can also check this page for game clones and/or remakes
 https://osgameclones.com/, some require compiling the source code.
 ___
 Freedos-user 

Re: [Freedos-user] retro gamer review of FreeDOS 1.3

[Carlos Teixeira]

Why FreeDOS if i can use other MS (and others) versions of DOS? 6.22 should
be the best option but, for a special purpose all rounder DOS computer i'm
using (because i lack the space to use several builds) FAT16B is too
limiting. With this in mind i have 2 options: strip DOS outta Windows 98SE
(or just use the CDU 7.1) or FreeDOS. Both allow FAT32.

Alas, FAT-32 MS-DOS introduces issues of its own with other games.
Starflight 1 and 2 have problems on these installed, and Tsunami Media
games (Man Enough, Return to Ringworld, just to name a few) refuse to run
completely. All these games Run flawlessly on FreeDOS. Considering i
already use several FreeDOS included drivers (CTMouse, mkeyb, HIMEMX, again
just to name a few) there's no reason why i and others can't aspire to use
FreeDOS with better compatibility and usability than the old unmaimtened
and closed source FAT32 DOS or even the older less feature packed 6.22.


So you downloaded some of those games and they ran but had speed issues and
exited with error code. Then you tried your Floppy versions and you report
black screen with no errors (same as others and me included had reported).
And you tested all this between 1.3rc4 and 1.3 live on a VM. Oh... You know
what? There's no point in continuing this discussion with you. The OP made
a thread about a video a retro gamer made testing FreeDOS compatibility
with some games on bare metal. This is just turning mind blowingly non
sequitur between DOSBox and VMs so, seriously, let's just end this.

A terça, 8/03/2022, 19:20, Joao Silva  escreveu:

> First of all i'm not Dude if more Sir or Mr.
> I don't know you and certainly i'm not your friend...
>
> Moving on... downloaded the games mentioned above and using my freedos
> 1.3-RC4 i was able to run Test Drive 2 and Grand Prix and Cycles ran the
> intro fast and exited with a error code.
> Test Drive 2 played and exited with a error.
>
> I grabbed my floppies with the same games (except for cycles) they did not
> run, got a black screen and no error output.
> Runnnig on a VM Freedos 1.3-RC4 and 1.3 Live
>
> And the final question what do you want with Freedos if you have and quote
> "
> I also can use from CP/M-86 to all MS-DOS oficial releases to Windows 98
> stripped FAT32 MS-DOS. PC-DOS, DR-DOS, whatever.
>
> "
>
> They should run games better than Freedos!
>
> On Mon, Mar 7, 2022 at 8:43 PM Carlos Teixeira 
> wrote:
>
>> Dude... I do have the right hardware from an original IBM XT to a couple
>> Turbo XT clones, to a Tandy 1000 SL that i had to mod for 220V, to a 286,
>> 386, 486 and Pentium MMX.
>>
>> I also can use from CP/M-86 to all MS-DOS oficial releases to Windows 98
>> stripped FAT32 MS-DOS. PC-DOS, DR-DOS, whatever. No point in discussing
>> DOSBox. The point here is:
>>
>> FreeDOS and its ability to run DOS games. In the case of DSI games,
>> there's something specific to the game engine that prevents those games
>> from running, GP Circuit, The Cycles and Test Drive 2. I've had no chance
>> yet but a good thing try might be running a debugger and checking if the
>> code might be stuck in an infinite loop.
>>
>> Planet X3, for instance, despite being programmed for XT class machines
>> that usually use MS-DOS 3.3, had a bug in which the game was stuck in an
>> infinite loop while printing a string just before exiting to DOS. So i took
>> a look into the code and what happened is that INT 29 might trash BX
>> completely which was actually used to point to memory and fetch the
>> characters for the string. BX gets completely trashed so the string never
>> finished and just printed crap on the screen. An isolated problem on a
>> specific version of DOS.
>>
>> This might be what is happening with the DSI games, or might be something
>> entirely different, but the fact that every game that uses the same engine
>> fails to run on FDOS makes it quite obvious that fixing just one of these
>> games will probably fix the rest. This is what we should focus on.
>>
>> A segunda, 7/03/2022, 13:04, Joao Silva  escreveu:
>>
>>> Hello!
>>>
>>> Not perfectly... for that you need the right hardware for the game to
>>> run, ms-dos 6.22 or pc-dos 7.0/7.1 and i'm assuming that you don't have
>>> either conditions.
>>>
>>> So dosbox will run most games, you can check the compatibility list
>>> https://www.dosbox.com/comp_list.php?letter=a  and fine tune the cpu
>>> speed on dosbox.
>>>
>>> You  can also check dosbox-x with more features.
>>>
>>> You can also check this page for game clones and/or remakes
>>> https://osgameclones.com/, some require compiling the source code.
>>> ___
>>> Freedos-user mailing list
>>> Freedos-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>>
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
> 

Re: [Freedos-user] retro gamer review of FreeDOS 1.3

[Joao Silva]

First of all i'm not Dude if more Sir or Mr.
I don't know you and certainly i'm not your friend...

Moving on... downloaded the games mentioned above and using my freedos
1.3-RC4 i was able to run Test Drive 2 and Grand Prix and Cycles ran the
intro fast and exited with a error code.
Test Drive 2 played and exited with a error.

I grabbed my floppies with the same games (except for cycles) they did not
run, got a black screen and no error output.
Runnnig on a VM Freedos 1.3-RC4 and 1.3 Live

And the final question what do you want with Freedos if you have and quote
"
I also can use from CP/M-86 to all MS-DOS oficial releases to Windows 98
stripped FAT32 MS-DOS. PC-DOS, DR-DOS, whatever.

"

They should run games better than Freedos!

On Mon, Mar 7, 2022 at 8:43 PM Carlos Teixeira 
wrote:

> Dude... I do have the right hardware from an original IBM XT to a couple
> Turbo XT clones, to a Tandy 1000 SL that i had to mod for 220V, to a 286,
> 386, 486 and Pentium MMX.
>
> I also can use from CP/M-86 to all MS-DOS oficial releases to Windows 98
> stripped FAT32 MS-DOS. PC-DOS, DR-DOS, whatever. No point in discussing
> DOSBox. The point here is:
>
> FreeDOS and its ability to run DOS games. In the case of DSI games,
> there's something specific to the game engine that prevents those games
> from running, GP Circuit, The Cycles and Test Drive 2. I've had no chance
> yet but a good thing try might be running a debugger and checking if the
> code might be stuck in an infinite loop.
>
> Planet X3, for instance, despite being programmed for XT class machines
> that usually use MS-DOS 3.3, had a bug in which the game was stuck in an
> infinite loop while printing a string just before exiting to DOS. So i took
> a look into the code and what happened is that INT 29 might trash BX
> completely which was actually used to point to memory and fetch the
> characters for the string. BX gets completely trashed so the string never
> finished and just printed crap on the screen. An isolated problem on a
> specific version of DOS.
>
> This might be what is happening with the DSI games, or might be something
> entirely different, but the fact that every game that uses the same engine
> fails to run on FDOS makes it quite obvious that fixing just one of these
> games will probably fix the rest. This is what we should focus on.
>
> A segunda, 7/03/2022, 13:04, Joao Silva  escreveu:
>
>> Hello!
>>
>> Not perfectly... for that you need the right hardware for the game to
>> run, ms-dos 6.22 or pc-dos 7.0/7.1 and i'm assuming that you don't have
>> either conditions.
>>
>> So dosbox will run most games, you can check the compatibility list
>> https://www.dosbox.com/comp_list.php?letter=a  and fine tune the cpu
>> speed on dosbox.
>>
>> You  can also check dosbox-x with more features.
>>
>> You can also check this page for game clones and/or remakes
>> https://osgameclones.com/, some require compiling the source code.
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos & Arachne

[andrea936]

  

Thanks, to you and Louis, 

 but also I have been using Links -g
for a long time and am quite satisfied. However, as freedos still has
Arachne in its package -in fdimples- and there is also a new release of
Arachne 1.99, I thought it was still usable in freedos ( I still
remember the polemic ten years ago on freedos -user -mailing about the
request to abandon Arachne from freedos.) 

regards 

andrea 

Il
08.03.2022 09:56 Björn Morell ha scritto: 

> I second that, Links 2.25
is nice especially on slower machines ( i run real ones , one 100 mhz
and one 1000 mhz). 
> Den 2022-03-08 kl. 07:05, skrev Louis Santillan:

> 
>> You might try Links2 Browser in graphics mode. 2.25 is the latest
version. 
>>
http://links.twibright.com/download/binaries/dos/links-2.25.exe [4] 
>>

>> On Mon, Mar 7, 2022 at 11:02 AM wrote: 
>> 
>>> Hi!
>>> I have used
Archne for a long time many years ago.
>>> Currently, both in freedos
1.2 and 1.3, ( no dosbox ) even with the latest release of Arachne it is
in fact impossible for me to use it.
>>> I know of arachne's well known
issues with https and jv, but it also seems to not recognize the normal
wattcp.cfg I use with links, lynx or gopherus. In fact I have to
manually set my ip address, nameserver, gateway and even then it is very
slow and often crashes. Even in off-line mode, for example as a .jpg
viewer, it is very slow and tends to freeze.
>>> Are there any
underlying incompatibilities with freedos? is the 16 bit problem? a
recognition problem from my ADSL fast fiber line?
>>> Yet, I repeat,
with my ethernet drivers both links and gopherus are fine and fast.
>>>
thanks Andrea 
>>> 
>>> Voucher MISE per P.IVA e PMI: fino a 2500EUR per
la Banda Ultralarga. https://www.tiscali.it/business/prodotti/voucher/
[1]
>>> 
>>> ___
>>>
Freedos-user mailing list
>>> Freedos-user@lists.sourceforge.net [2]
>>>
https://lists.sourceforge.net/lists/listinfo/freedos-user [3]
>> 
>>
___
>> Freedos-user mailing
list
>> Freedos-user@lists.sourceforge.net [6]
>>
https://lists.sourceforge.net/lists/listinfo/freedos-user [7]
 



Voucher MISE per P.IVA e PMI: fino a 2500€ per la Banda Ultralarga. 
https://www.tiscali.it/business/prodotti/voucher/?r=TS0A00025=link=tiscali_source=tiscali_medium=link_campaign=voucherbusiness_content=voucherbusiness_np=tiscali.link.footermail.voucher.business.btb.

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Announcement: lDebug release 4

[C. Masloch]

Hello list,

today I finished release 4 of my libre 86 DOS debugger called lDebug [1].

This release fixes several bugs, including several in the interactive 
enter mode (E command), one of which was reported in January to the 
original Debug/X project [2]. (lDebug is a fork originally based on 
FreeDOS Debug/X version 1.13 of 2008-02-27.) A major new feature is that 
the DI command (Dump Interrupt handler) now allows to follow downlinks 
of IBM Interrupt Sharing Protocol (IISP, [3]) headers, and can 
optionally also walk all Alternate Multiplex Interrupt Specification 
(AMIS, [4]) multiplexers' interrupt lists to find and identify handlers 
belonging to an interrupt's handler chain.


The entire news are listed in the manual, available in the release 
archives as well as on the web [5]. As usual, there are a tarball 
(lzip-compressed), a zip file, and a FreeDOS package zip file available 
in the lDebug download subdirectories on the server I use [6]. 
Additionally, there are now "current" release zipfiles available on the 
server. They are automatically updated daily, if changes were committed 
to the hg repo. There's ldebug.zip for the debugger proper [7] and 
lddebug.zip for the debuggable build of the debugger [8]. (You only want 
to use the debuggable build if you intend to debug the debugger itself.)


Regards,
ecm


[1]: https://pushbx.org/ecm/web/#projects-ldebug
[2]: https://github.com/Baron-von-Riedesel/DOS-debug/pull/4
[3]: https://pushbx.org/ecm/test/2020/intshare/INTSHARE.DOC
[4]: https://fd.lod.bz/rbil/zint/index_2d.html
[5]: https://pushbx.org/ecm/doc/ldebug.htm#news-r4
[6]: https://pushbx.org/ecm/download/ldebug/
[7]: https://pushbx.org/ecm/download/ldebug.zip
[8]: https://pushbx.org/ecm/download/lddebug.zip


___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] retro gamer review of FreeDOS 1.3

[Joao Silva]

Hello.
The man issues are related to msi dos games like gprix on FreeDOS not
working. De emulator would solve the issue, but he have all the hardware
and other msdos.

Noted i'll never mention dosbox and/or dosbox-x and shall be referred as
emulator.

Thank you.

On Tue, Mar 8, 2022, 00:16 Jim Hall  wrote:

> On Sun, Mar 6, 2022 at 11:44 AM Joao Silva  wrote:
> >
> > Hello.
> >
> > Dosbox will solve all your problems!
> >
>
>
> FYI
>
> From the list rules:
>
>Remember, this group is about FreeDOS. General DOS topics are okay,
>but try to keep it related to FreeDOS.
>
>
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Fdnet

[Björn Morell]

Den 2022-03-08 kl. 12:55, skrev Jerome Shidel:



On Mar 8, 2022, at 4:44 AM, Björn Morell  wrote:

I run MTCP and have for a while and it works great, ftp server etc. I have 
fresh installatio of 1.3 on an

old fujitsi-siemens 1000 mhz, with an intel 815 chipset so the e1000pkt works 
fine with DHCP and it

updates the .cfg. I ran the wattcp.bat and have a wattcp.cfg in freedos\bin. 
Paths to wattcp and MTCP

cfgs in fdauto.bat and this, as suggested in freedos wiki instructions, fdauto:

"if not exist %dosdir%\bin\fdnet.bat goto NoNetwork

e1000pkt 0x60

call %dosdir%\bin\fdnet.bat start

c:\ddhcp\ddhcp /w /f"

But i get this at boot (ftpsrv, browsing etc. works though) ;


"

Packet Driver for Intel (R) PRO/1000 Family of Desktop & Server adapters v0.50

Copyright (C) Intel Corportation 2006. All rights reserved.

PCI BIOS is required for this driver

HERE COMES THE STRANGE PART

Physical network not supported at the moment (My translation from swedish).

IP address : 192.168.1.247

Netmask   : 255.255.255.0

Gateway   : 192.168.1.1

DNS sever : 192.168.1.1

Lease time: 43200 "


What am I doing wrong to get the same Message as before I configured anything ?

things work though !

Have good day :)

FDNET only supports a select set of drivers. It is displaying that message.

Since, networking is configured, you are manually loading a packet driver and 
manually configuring dhcp, there really is no reason to call FDNET.

Simply REM the call to FDNET. It will prevent the message.



Bear


Thanx for prompt answer,

Yes I figured it was no biggy :)  Many things will be gone from 
Fdauto.bat, not necessary with all the batch files the original goes 
through.



Bear








___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Fdnet

[Jerome Shidel]

> On Mar 8, 2022, at 4:44 AM, Björn Morell  wrote:
> 
> I run MTCP and have for a while and it works great, ftp server etc. I have 
> fresh installatio of 1.3 on an
> 
> old fujitsi-siemens 1000 mhz, with an intel 815 chipset so the e1000pkt works 
> fine with DHCP and it
> 
> updates the .cfg. I ran the wattcp.bat and have a wattcp.cfg in freedos\bin. 
> Paths to wattcp and MTCP
> 
> cfgs in fdauto.bat and this, as suggested in freedos wiki instructions, 
> fdauto:
> 
> "if not exist %dosdir%\bin\fdnet.bat goto NoNetwork
> 
> e1000pkt 0x60
> 
> call %dosdir%\bin\fdnet.bat start
> 
> c:\ddhcp\ddhcp /w /f"
> 
> But i get this at boot (ftpsrv, browsing etc. works though) ;
> 
> 
> "
> 
> Packet Driver for Intel (R) PRO/1000 Family of Desktop & Server adapters v0.50
> 
> Copyright (C) Intel Corportation 2006. All rights reserved.
> 
> PCI BIOS is required for this driver
> 
> HERE COMES THE STRANGE PART
> 
>Physical network not supported at the moment (My translation from swedish).
> 
> IP address : 192.168.1.247
> 
> Netmask   : 255.255.255.0
> 
> Gateway   : 192.168.1.1
> 
> DNS sever : 192.168.1.1
> 
> Lease time: 43200 "
> 
> 
> What am I doing wrong to get the same Message as before I configured anything 
> ?
> 
> things work though !
> 
> Have good day :)

FDNET only supports a select set of drivers. It is displaying that message.

Since, networking is configured, you are manually loading a packet driver and 
manually configuring dhcp, there really is no reason to call FDNET. 

Simply REM the call to FDNET. It will prevent the message. 


> 
> Bear
> 
> 
> 
> 
> 
> 
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] Fdnet

[Björn Morell]

I run MTCP and have for a while and it works great, ftp server etc. I 
have fresh installatio of 1.3 on an


old fujitsi-siemens 1000 mhz, with an intel 815 chipset so the e1000pkt 
works fine with DHCP and it


updates the .cfg. I ran the wattcp.bat and have a wattcp.cfg in 
freedos\bin. Paths to wattcp and MTCP


cfgs in fdauto.bat and this, as suggested in freedos wiki instructions, 
fdauto:


"if not exist %dosdir%\bin\fdnet.bat goto NoNetwork

e1000pkt 0x60

call %dosdir%\bin\fdnet.bat start

c:\ddhcp\ddhcp /w /f"

But i get this at boot (ftpsrv, browsing etc. works though) ;


"

Packet Driver for Intel (R) PRO/1000 Family of Desktop & Server adapters 
v0.50


Copyright (C) Intel Corportation 2006. All rights reserved.

PCI BIOS is required for this driver

HERE COMES THE STRANGE PART

   Physical network not supported at the moment (My translation from 
swedish).


IP address : 192.168.1.247

Netmask   : 255.255.255.0

Gateway   : 192.168.1.1

DNS sever : 192.168.1.1

Lease time: 43200 "


What am I doing wrong to get the same Message as before I configured 
anything ?


things work though !

Have good day :)

Bear






___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] Freedos & Arachne

[Björn Morell]

I second that, Links 2.25 is nice especially on slower machines ( i run 
real ones , one 100 mhz and one 1000 mhz).


Den 2022-03-08 kl. 07:05, skrev Louis Santillan:
You might try Links2 Browser in graphics mode. 2.25 is the latest 
version.


http://links.twibright.com/download/binaries/dos/links-2.25.exe

On Mon, Mar 7, 2022 at 11:02 AM  wrote:



Hi!
I have used Archne for a long time many years ago.
Currently, both in freedos 1.2 and 1.3, ( no dosbox ) even with
the latest release of Arachne it is in fact impossible for me to
use it.
 I know of arachne's well known issues with https and jv, but it
also seems to not recognize the normal wattcp.cfg I use with
links, lynx or gopherus. In fact I have to manually set my ip
address, nameserver, gateway and even then it is very slow and
often crashes. Even in off-line mode, for example as a .jpg
viewer, it is very slow and tends to freeze.
 Are there any underlying incompatibilities with freedos? is the
16 bit problem? a recognition problem from my ADSL fast fiber line?
Yet, I repeat, with my ethernet drivers both links and gopherus
are fine and fast.
thanks Andrea



Voucher MISE per P.IVA e PMI: fino a 2500€ per la Banda
Ultralarga. https://www.tiscali.it/business/prodotti/voucher/



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user



___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user