[Freedos-user] freedos 1.3 on vm or real machine

2022-03-10 Thread Joao Silva
Hello I have a question: on freedos 1.3 or 1.2 i can't write the * without going to the numeric keypad. KEYB PO,858 available: 858, 850, 860 also can't write: ã ä â á à ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net

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

2022-03-10 Thread Carlos Teixeira
I use a Pentium MMX as my fastest dedicated PC for DOS and i usually downclock it to 50MHz FSB x 2. If some games still have issues i can use SETMUL to manipulate Pentium TR4 registers, which allow to disable exclusively CPU features like Instruction Cache, Data Cache, Branch Prediction and

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

2022-03-10 Thread Bret Johnson
I heard/read somewhere that the "Runtime Error 200" was actually caused some sort of subroutine that was trying to figure out how fast the computer is. It's certainly ironic that it doesn't work on really fast computers since that's exactly the "problem" it's trying to address. The other

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

2022-03-10 Thread Joao Silva
Hello. Thank you Eric and Jim. I'll do a search and i let you know how it turned out On Thu, Mar 10, 2022 at 10:04 AM Jim Hall wrote: > One program to fix the "runtime error 200" is Robert and Marek's TSR tool, > which we include in FreeDOS 1.3: > >

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

2022-03-10 Thread Jim Hall
One program to fix the "runtime error 200" is Robert and Marek's TSR tool, which we include in FreeDOS 1.3: http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/repositories/1.3/pkg-html/tp7p5fix.html But as Eric said, you can find lots of tools on the Internet to fix this too. Or you can run

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

2022-03-10 Thread Eric Auer
Hi! Runtime error 200 usually is an overflow in timing code of Borland or Turbo Pascal, if you search the web you will find various tools which patch it or work it around :-) The overflow happens because your computer is too fast. So you can also try to slow it down, e.g. using FDAPM SPEEDn