It's not really a bug. The game is designed so that if you try to cheat by
exiting a game without forfeiting it, it doesn't work.
And I believe that many many many people are playing my out dated code as you
called it just perfectly fine on computers running everything from 98 to 7 64
----- Original Message -----
Well those are just a few of the hidden bugs when using outdated code
on a higher op.
At 09:27 PM 4/16/2011, you wrote:
That's not going to resolve the problem. I've got the latest VB 6
libs, and still get a runtime error 13. I've already explained what
causes that error. It is caused by passing a value to a variable when
it is the wrong datatype.
My guess here is since Jim doesn't use datatyping himself what he did
is passed a value to a variable such as an integer like 5, and then
later tried to pass an incompatible datatype like a float, double,
string, etc to that variable later on and the program blows up. The
variable in question currently is asigned an integer value or
something like that, and has only reserved enough memory for an
integer value, and he tried to reasign it after it was asigned a
different datatype and the runtime basically comes back saying
"Ummm...This ain't legal code dude!"
On 4/16/11, shaun everiss <sm.ever...@gmail.com> wrote:
> maybe you need the latest vb6sp5 libs from ms they should still
> exist somewhere.
> I know the dxvb stuff is loaded by jim's setup and this shouldn't
> happen on older oses.
Check my web site for my free blind accessible pc dos and windows games.
Chardon Ohio USA
Gamers mailing list __ Gamers@audyssey.org
If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org.
You can make changes or update your subscription via the web, at
All messages are archived and can be searched and read at
If you have any questions or concerns regarding the management of the list,
please send E-mail to gamers-ow...@audyssey.org.