Norton's System Information for DOS
Bengoa Altick
I don't know what happened to my news server.
It gives all posts in this group as:
Error!
newsgroup server responded:Bad article number
Perhaps the article has expired
I know they have at least a 2 month retention.
So I begin a new treat.
Thank you for SYSINFO.EXE.
I could not run it because it asks for another file:
Enter directory for
NLIBE200.RTL
This file was not necessary in the old SI.EXE
Alejandro Lieber
Rosario Argentina
http://lieber.com.ar
Richard Bonner
> Richard:
> I don't know what happened to my news server.
> It gives all posts in this group as:
> Error!
> newsgroup server responded:Bad article number
> Perhaps the article has expired
> I know they have at least a 2 month retention.
*** It may be less if traffic has increased on that server.
> So I begin a new treat.
> Thank you for SYSINFO.EXE.
*** You're welcome.
> I could not run it because it asks for another file:
> Enter directory for
> NLIBE200.RTL
> This file was not necessary in the old SI.EXE
> Alejandro Lieber
*** E-mail me again and I will send the library file to you.
--
Richard Bonner
http://www.chebucto.ca/~ak621/DOS/
Alejandro Lieber
It does't work.
It gives the typical error of old DOS programs trying to run in new
machines:
Your program caused a divide overflow error.
Alejandro
Richard Bonner wrote:
Richard Bonner
> Richard:
> It does't work.
> It gives the typical error of old DOS programs trying to run in new
> machines:
> Your program caused a divide overflow error.
> Alejandro
*** You can use SLOWDOWN or similar programs to enable SI.exe to
run on faster systems, but any processor speed specs it presented would be
wrong.
John Stockton once suggested a better solution than using SLOWDOWN, but
I can't remember what it was. John: are you reading?
One or more links to websites
for the referred program(s)
can be found at:
http://www.chebucto.ca/~ak621/DOS/Websites.html
Klaus Meinhard
>> Your program caused a divide overflow error.
> *** You can use SLOWDOWN or similar programs to enable SI.exe to
> run on faster systems, but any processor speed specs it presented
> would be wrong.
There are patch programs for this error. Any use of Google with "runtime
eror 200" or "dos divide overflow" will suffice.
--
Herzliche Gr��e,
Klaus Meinhard
Dr J R Stockton
16 Oct 2009 13:34:24, Richard Bonner <ak...@chebucto.ns.ca> posted:
>Alejandro Lieber (alej...@invalid.net.ar) wrote:
>> Richard:
>
>> It does't work.
>
>> It gives the typical error of old DOS programs trying to run in new
>> machines:
>
>> Your program caused a divide overflow error.
>
>> Alejandro
>
>*** You can use SLOWDOWN or similar programs to enable SI.exe to
>run on faster systems, but any processor speed specs it presented would be
>wrong.
Not a good recommendation nowadays, in c21.
> John Stockton once suggested a better solution than using SLOWDOWN, but
^^^^ gross underestimate!
>I can't remember what it was. John: are you reading?
And what if I replied "No"? Just cite the c.l.p.b mFAQ and/or my site.
AL did not give the exact error message and (if you are right) mis-
described it.
Also, Error 200 mis-describes itself. What the error-detector actually
detects is something which, in the opinion of the error-message author,
can only be given by divide overflow. In fact, it can only be given in
compiled Pascal by divide overflow. As you know, assembly code is more
versatile in hoe it can fail.
Google on Runtyme eror 200 (misspelt here to reduce future finds)
or 200 dyvyde oberfluw (ditto).
Use Bauer on EXEs, and Scragg when compiling.
--
(c) John Stockton, nr London UK. ?@merlyn.demon.co.uk Turnpike v6.05 MIME.
<URL:http://www.merlyn.demon.co.uk/> TP/BP/Delphi/&c., FAQqy topics & links;
<URL:http://www.merlyn.demon.co.uk/clpb-faq.txt> RAH Prins : c.l.p.b mFAQ;
<URL:ftp://garbo.uwasa.fi/pc/link/tsfaqp.zip> Timo Salmi's Turbo Pascal FAQ.
Richard Bonner
> Richard Bonner <ak...@chebucto.ns.ca> posted:
> >Alejandro Lieber (alej...@invalid.net.ar) wrote:
> >> Richard:
> >
> >> Your program caused a divide overflow error.
> >
> >> Alejandro
> >
> >*** You can use SLOWDOWN or similar programs to enable SI.exe to
> >run on faster systems, but any processor speed specs it presented would be
> >wrong.
> Not a good recommendation nowadays, in c21.
> > John Stockton once suggested a better solution than using SLOWDOWN, but
> ^^^^ gross underestimate!
*** Sorry, I wasn't thinking when I typed that.
> >I can't remember what it was. John: are you reading?
> And what if I replied "No"?
*** Then we'd know you weren't reading this thread. (-:
> Just cite the c.l.p.b mFAQ and/or my site.
(Snip)
> --
> (c) John Stockton
*** I will remember that for the next time.
Richard Bonner
> >> Your program caused a divide overflow error.
> > *** You can use SLOWDOWN or similar programs to enable SI.exe to
> > run on faster systems, but any processor speed specs it presented
> > would be wrong.
> There are patch programs for this error. Any use of Google with "runtime
> eror 200" or "dos divide overflow" will suffice.
> --
> Klaus Meinhard
*** Thanks, Klaus. I haven't tried one for `SI.exe' because I don't need
it, but in the past, I have not had a lot of success with some of the
patch programs I have tried for other executables. Even when they have
worked, they introduced errors or created conflicts and so I had to drop
them. Perhaps this is because I have so much stuff running that interacts
with one another.
The nice thing about SLOWDOWN is that it works with any executable and
it also allows me to vary the rate while a program is running.
Klaus Meinhard
> The nice thing about SLOWDOWN is that it works with any executable
> and it also allows me to vary the rate while a program is running.
Yes, and it slows down the whole computer, thus making all that dearly
bought progress in CPU speed void. Ideally you should run old DOS
proggies on old 286 / 386 machines.
I have no experience with the diverse patching programms. I believe most
of them were for Turbo Pascal. I wouldn't be surprised if programs
patched for runtime error 200 ran into other problems later on.
--
Best Regards,
* Klaus Meinhard *
<www.4dos.info>
Richard Bonner
Richard said:
> > The nice thing about SLOWDOWN is that it works with any executable
> > and it also allows me to vary the rate while a program is running.
> Yes, and it slows down the whole computer, thus making all that dearly
> bought progress in CPU speed void.
*** If I am multitasking, this can be a problem. However, I am mostly
using it for games, so I am concentrating on them at the time and don't
think I ever run anything in the background while playing games.
Now, if I happen to open another DOS session, I can simply press
Ctrl-alt-0 and the CPU speed is restored to full speed until I change it.
Also, after I close any given program using SLOWDOWN, the batch file that
started the program, will remove SLOWDOWN from memory automatically. It's
very smooth and I don't think much about it anymore because it happens
all on its own.
> Ideally you should run old DOS proggies on old 286 / 386 machines.
*** That is too much extra work and space for me to bother. It's a
simple thing to code SLOWDOWN into the batch files I use to run programs
requiring it, which by the way are very few. I think I might use it on
five or six programs total.
> I have no experience with the diverse patching programms. I believe most
> of them were for Turbo Pascal. I wouldn't be surprised if programs
> patched for runtime error 200 ran into other problems later on.
> --
> * Klaus Meinhard *
*** I have not tried any of them in years. Perhaps they have improved.
Dr J R Stockton
10 Nov 2009 09:32:48, Klaus Meinhard <K_Mei...@gmx.de> posted:
They do not, unless they try to do something OK in (say) DOS 6.2 but not
in Windows, which is an entirely different matter.
Read before Write! You get the answers more quickly that way!!
Pascal Start-Up Error 200 on fast PCs when using the Crt unit is a VFAQ!
Read the regularly-posted newsgroup FAQ.
Read the many earlier postings in the comp.lang.pascal.borland (Frank H,
Roger D, Pedt S, Osmo R, ...) and borland.public.turbopascal newsgroups
(you could use Google?), including the comp.lang.pascal.borland mini-FAQ
(a copy is at <URL: http://www.merlyn.demon.co.uk/clpb-faq.txt >; and Prof.
Salmi's FAQ ftp://garbo.uwasa.fi/pc/link/tsfaqp.zip #124, and/or Ing.
Franz Glaser's http://www.geocities.com/SiliconValley/2926/tp.html and my
http://www.merlyn.demon.co.uk/ pas-time.htm pas-r200.htm pas-wait.htm .
Install Pedt Scragg's Crt unit; or Robert Prins' CRT unit;
or run Andreas Bauer's TPPATCH on your EXE (beware early c't EXE-patches).
Other fixes are to avoid all use of the Crt unit; or, if accurate Delay
is not needed, to compile with TP5 or TP6.
--
� John Stockton, Surrey, UK. ???@merlyn.demon.co.uk Turnpike v6.05 MIME.
Klaus Meinhard
> Read before Write! You get the answers more quickly that way!!
My message was tailing a thread where the relevant answers had already
been given. I was not looking for any error 200 answers. Try not to
shoot refelexively from the hip. :-)
>... and/or Ing. Franz
> Glaser's http://www.geocities.com/SiliconValley/2926/tp.html
... is no longer available. Check you links! :-)
Herzliche Gr��e,
Klaus Meinhard
Dr J R Stockton
13 Nov 2009 11:44:36, Klaus Meinhard <K_Mei...@gmx.de> posted:
>Hallo J R Stockton,
>
>> Read before Write! You get the answers more quickly that way!!
>
>My message was tailing a thread where the relevant answers had already
>been given. I was not looking for any error 200 answers. Try not to
>shoot refelexively from the hip. :-)
You wrote, and I quoted, "I have no experience with the diverse patching
programms. I believe most of them were for Turbo Pascal. I wouldn't be
surprised if programs patched for runtime error 200 ran into other
problems later on."
As a report of your internal mental state, one can believe those
statements.
But your internal state is unimportant. Your inexperienced advice is of
negative worth, being based upon delusion.
Early patches released by some foreign magazine - C't of Germany IIRC -
transferred the failure from a CPU clock rate about 200 MHz to one a few
times higher. But the good work, which I referred to, does not fail at
ant reasonable CPU frequency : I think Scragg's library routine is good
to at least 100 GHz, and I've seen no problem with the patch of your
compatriot Andreas Bauer.
>>... and/or Ing. Franz
>> Glaser's http://www.geocities.com/SiliconValley/2926/tp.html
>
>... is no longer available. Check you links! :-)
It is available - you forget the Wayback Machine.
Klaus Meinhard
<sigh>
> You wrote, and I quoted, "I have no experience with the diverse
> patching programms. I believe most of them were for Turbo Pascal. I
> wouldn't be surprised if programs patched for runtime error 200 ran
> into other problems later on."
>
> As a report of your internal mental state, one can believe those
> statements.
>
> But your internal state is unimportant. Your inexperienced advice is
> of negative worth, being based upon delusion.
Since you obstinately refuse to read the threads before latching onto an
isolated remark , I'll try to enlighten you:
Richard Bonner wrote on 09.11.2009:
< Thanks, Klaus. I haven't tried one for `SI.exe' because I don't need
it, but in the past, I have not had a lot of success with some of the
patch programs I have tried for other executables. Even when they have
worked, they introduced errors or created conflicts and so I had to drop
them. Perhaps this is because I have so much stuff running that
interacts
with one another. >
My answer just stated that imho its possible that other conflicts not
dependant on error 200 may occur in these old programs. At this stage of
my exchange with Richard accurate advice to the OP had long been given.
The only illusions around here are yours: the illusion that your input
was wanted, useful or accurate.
--
Best Regards,
* Klaus Meinhard *
<www.4dos.info>
>