Back to the main page

Mailing List Logs for ShadowRN

Message no. 1
From: shadowrn@*********.com (Derek Hyde)
Subject: [OT] Dumpshock Site Software
Date: Mon Feb 4 15:10:01 2002
Umm....someone help me out here...I've got a brand new computer with all
of the VB6 stuff already installed....why in the world are the programs
that I'm finding on the dumpshock site telling me that they won't work
unless I download the VB 3 runtime files?????

(one would assume that a system with a 2000+ Athlon XP processor, 1GB of
PC2100 DDR, Windows XP, 4 80GB 10,000 RPM SCSI HD's and a 20GB UATA100
HD would be more than capable of handling anything out there but I'm
finding things quite to the contrary)
Message no. 2
From: shadowrn@*********.com (Jonathan)
Subject: [OT] Dumpshock Site Software
Date: Mon Feb 4 15:45:01 2002
----- Original Message -----
From: "Derek Hyde" <dhyde@*********.net>
To: <shadowrn@*********.com>
Sent: Monday, February 04, 2002 4:41 PM
Subject: [OT] Dumpshock Site Software


> Umm....someone help me out here...I've got a brand new computer with all
> of the VB6 stuff already installed....why in the world are the programs
> that I'm finding on the dumpshock site telling me that they won't work
> unless I download the VB 3 runtime files?????
>

Actually it's a compatibility issue. Programs written in older
languages/versions often don't mesh well with newer. Games are a sign of
this...quake 3 is in patch version 1.31 any mods coded with 1.30 or earlier
won't work with 1.31 code.

Yes it's silly but when you think about it it makes a...warped...kind of
sense. With new versions come improved code. This new code sometimes
requires a complete re-working of earlier parts. Older code look for the
older workings but instead finds the newer pieces and is confused...hence
download older version request.

It's dumb but then again it's not uncommon.

System specs aside...you could have the end all of computers...and someone
will create a program that will require that plus something else to make it
incompatible. It's the lovely world of computers. :-)
Message no. 3
From: shadowrn@*********.com (Mik)
Subject: [OT] Dumpshock Site Software
Date: Mon Feb 4 16:15:01 2002
AT LAST !!

someone else with the same problem i have :)

Win2k, VB6 Pro, VB Runtime SP5, Dual 1ghz P3's + 1gb DDRRam.

anyone out there with a solution ??? PLEASE ???

Mik
Lurker of Oz


----- Original Message -----
From: "Derek Hyde" <dhyde@*********.net>
To: <shadowrn@*********.com>
Sent: Tuesday, February 05, 2002 7:11 AM
Subject: [OT] Dumpshock Site Software


> Umm....someone help me out here...I've got a brand new computer with all
> of the VB6 stuff already installed....why in the world are the programs
> that I'm finding on the dumpshock site telling me that they won't work
> unless I download the VB 3 runtime files?????
>
> (one would assume that a system with a 2000+ Athlon XP processor, 1GB of
> PC2100 DDR, Windows XP, 4 80GB 10,000 RPM SCSI HD's and a 20GB UATA100
> HD would be more than capable of handling anything out there but I'm
> finding things quite to the contrary)
>
>
Message no. 4
From: shadowrn@*********.com (Jonathan)
Subject: [OT] Dumpshock Site Software
Date: Mon Feb 4 16:25:01 2002
> AT LAST !!
>
> someone else with the same problem i have :)
>
> Win2k, VB6 Pro, VB Runtime SP5, Dual 1ghz P3's + 1gb DDRRam.
>
> anyone out there with a solution ??? PLEASE ???
>

Solution: BAck up any files those runtime components want to replace then
download the older files. When finished revert to back ups.

Other than that:

Find someone to recode a VB3 application in VB6...

:o)
Message no. 5
From: shadowrn@*********.com (Jason Lantrip)
Subject: [OT] Dumpshock Site Software
Date: Mon Feb 4 16:25:04 2002
>>anyone out there with a solution ??? PLEASE ???

I'm not 100% certain (I'm a network admin, not a programmer), but...

You'll probably need to find the older VB3/4 runtime files (there's a few
site on the 'net, if you search Google). There was a change after
VB4...having the newest, most current VB runtime files won't do you any
good, since they're not the files the older programs use.

That's the case in my office, anyway, where we use both newer and older
VB-written software...

--Jason
Message no. 6
From: shadowrn@*********.com (Derek Hyde)
Subject: [OT] Dumpshock Site Software
Date: Mon Feb 4 16:45:01 2002
> Other than that:
>
> Find someone to recode a VB3 application in VB6...
umm...hehe....ok.....

ANYONE HERE WANT TO RECODE THE DECKER PROGRAM FROM VB whatever TO
VB6???????

I'll give you some oreos??
Message no. 7
From: shadowrn@*********.com (Peter Kristiansen)
Subject: [OT] Dumpshock Site Software
Date: Mon Feb 4 17:35:01 2002
From: "Derek Hyde" <dhyde@*********.net>

> ANYONE HERE WANT TO RECODE THE DECKER PROGRAM FROM VB
> whatever TO VB6???????
>
I haven't looked at the program myself, but does it come with the source
code??
If it does I can try to recompile it under VB6.

Peter.
Message no. 8
From: shadowrn@*********.com (Adam Jury)
Subject: [OT] Dumpshock Site Software
Date: Mon Feb 4 22:20:01 2002
On Mon, 4 Feb 2002, Derek Hyde wrote:

> Umm....someone help me out here...I've got a brand new computer with all
> of the VB6 stuff already installed....why in the world are the programs
> that I'm finding on the dumpshock site telling me that they won't work
> unless I download the VB 3 runtime files?????

The VB runtime files aren't backwards compatible; there's a seperate DLL
or two for each version of VB - grab vbrun300.dll and any other
necessary files listed and you should be just fine.

[Updateding VB3/4 apps to VB6 tends to not be a trivial process, because
many of the "common controls" like tabbed dialogs have changed
substantially in the years.]

Adam
Message no. 9
From: shadowrn@*********.com (Jonathan)
Subject: [OT] Dumpshock Site Software
Date: Mon Feb 4 22:50:00 2002
> The VB runtime files aren't backwards compatible; there's a seperate DLL
> or two for each version of VB - grab vbrun300.dll and any other
> necessary files listed and you should be just fine.
>
> [Updateding VB3/4 apps to VB6 tends to not be a trivial process, because
> many of the "common controls" like tabbed dialogs have changed
> substantially in the years.]
>

ehhhh hasn't changed THAT much. The syntax was adjusted and the layout of
the coding application has changed but Visual Basic is still Visual Basic.
:-) I do admit though recoding an application from scratch would ultimately
result in a whole new application it wouldn't be viciously hard to do (it is
VB after all), would go alot faster with the previous versions source code.
(And hoping to god that the coder used realistic naming conventions rather
than naming conventions of old - variables with letter/number combinations
that make 2nd party updating a major pain in the ass)

*Shudders remembering trying to update a billing application in
Access...naming conventions with no meaning and no tech manual left by the
original coder...*
Message no. 10
From: shadowrn@*********.com (Gurth)
Subject: [OT] Dumpshock Site Software
Date: Tue Feb 5 08:05:01 2002
According to Derek Hyde, on Mon, 04 Feb 2002 the word on the street was...

> Umm....someone help me out here...I've got a brand new computer with all
> of the VB6 stuff already installed....why in the world are the programs
> that I'm finding on the dumpshock site telling me that they won't work
> unless I download the VB 3 runtime files?????

Because the two aren't compatible. If a program is written in a given
version of Visual Basic, it requires the runtimes for _that_ VB version,
not a later one. This is especially true for VB3 stuff, because that's a
16-bit version (for Windows 3.x) while later versions are 32-bit (for
Windows 95 -- yeah, I know there was a 16-bit VB4).

> (one would assume that a system with a 2000+ Athlon XP processor, 1GB of
> PC2100 DDR, Windows XP, 4 80GB 10,000 RPM SCSI HD's and a 20GB UATA100
> HD would be more than capable of handling anything out there but I'm
> finding things quite to the contrary)

Of course it is -- just download the runtimes, install them, and it'll be
able to handle it. The junk that's in your computer doesn't matter one bit,
when you get down to it.

--
Gurth@******.nl - http://www.xs4all.nl/~gurth/index.html
That's the way that I can't win.
-> NAGEE Editor * ShadowRN GridSec * Triangle Virtuoso <-
-> The Plastic Warriors Page: http://plastic.dumpshock.com <-

GC3.12: GAT/! d- s:- !a>? C++@ UL+ P(+) L++ E W--(++) N o? K w(--) O
V? PS+ PE@ Y PGP- t@ 5++ X(+) R+++$ tv+(++) b++@ DI- D+ G+ e h! !r y?
Incubated into the First Church of the Sqooshy Ball, 21-05-1998
Message no. 11
From: shadowrn@*********.com (Gurth)
Subject: [OT] Dumpshock Site Software
Date: Tue Feb 5 08:05:14 2002
According to Jonathan, on Tue, 05 Feb 2002 the word on the street was...

> ehhhh hasn't changed THAT much. The syntax was adjusted and the layout of
> the coding application has changed but Visual Basic is still Visual
> Basic.

The actual code usually isn't the problem; the hard part is the fact that
you usually have to use newer versions of any OCXs you used in the app,
which in turn half the time require you to totally re-do the controls
because they can't automatically upgrade themselves. Say you've used a tab
control in a VB4 app, and now load that same app into VB6; you're now going
to have to delete the tab, and replace it by the VB6 equivalent cobtrol --
and so put in all its settings again, make sure the code is in the right
places, adjust your code because some property names or methods have
changed, and so on.

--
Gurth@******.nl - http://www.xs4all.nl/~gurth/index.html
That's the way that I can't win.
-> NAGEE Editor * ShadowRN GridSec * Triangle Virtuoso <-
-> The Plastic Warriors Page: http://plastic.dumpshock.com <-

GC3.12: GAT/! d- s:- !a>? C++@ UL+ P(+) L++ E W--(++) N o? K w(--) O
V? PS+ PE@ Y PGP- t@ 5++ X(+) R+++$ tv+(++) b++@ DI- D+ G+ e h! !r y?
Incubated into the First Church of the Sqooshy Ball, 21-05-1998
Message no. 12
From: shadowrn@*********.com (George S Waksman)
Subject: [OT] Dumpshock Site Software
Date: Tue Feb 5 08:55:03 2002
"Derek Hyde" wrote:

>Umm....someone help me out here...I've got a brand new computer with all
>of the VB6 stuff already installed....why in the world are the programs
>that I'm finding on the dumpshock site telling me that they won't work
>unless I download the VB 3 runtime files?????
>
>(one would assume that a system with a 2000+ Athlon XP processor, 1GB of
>PC2100 DDR, Windows XP, 4 80GB 10,000 RPM SCSI HD's and a 20GB UATA100
>HD would be more than capable of handling anything out there but I'm
>finding things quite to the contrary)
>
>

The Visual Basic runtime DLLs are not backwards compatible. It doesn't matter how good
your computer is, you can't run a VB3 program with the VB6 DLLs. Go find yourself a copy
of the VB3 DLLs (they're free and readily available).

-George Waksman
Message no. 13
From: shadowrn@*********.com (Jonathan)
Subject: [OT] Dumpshock Site Software
Date: Tue Feb 5 10:00:01 2002
> The actual code usually isn't the problem; the hard part is the fact that
> you usually have to use newer versions of any OCXs you used in the app,
> which in turn half the time require you to totally re-do the controls
> because they can't automatically upgrade themselves. Say you've used a tab
> control in a VB4 app, and now load that same app into VB6; you're now
going
> to have to delete the tab, and replace it by the VB6 equivalent cobtrol --
> and so put in all its settings again, make sure the code is in the right
> places, adjust your code because some property names or methods have
> changed, and so on.
>
> --

True enough, what did these programs do anyways?
Message no. 14
From: shadowrn@*********.com (Peter Kristiansen)
Subject: [OT] Dumpshock Site Software
Date: Tue Feb 5 16:30:01 2002
From: "Peter Kristiansen" <psk@*****.stofanet.dk>
> I haven't looked at the program myself, but does it come with the
source
> code??
> If it does I can try to recompile it under VB6.

I've looked through the code now, and just as I feared I have to agree
with Adam J and Gurth.

They have changed quite a deal of things which means that it's
infinitely easier for all of you to find vbrun300.dll and put that in
your system dir than for anyone to try to port this to VB6.

Peter
- who doesn't know vb3 but - unfortunately - knows vb6...
Message no. 15
From: shadowrn@*********.com (Derek Hyde)
Subject: [OT] Dumpshock Site Software
Date: Tue Feb 5 17:00:02 2002
> I've looked through the code now, and just as I feared I have to agree
> with Adam J and Gurth.
>
> They have changed quite a deal of things which means that it's
> infinitely easier for all of you to find vbrun300.dll and put that in
> your system dir than for anyone to try to port this to VB6.
>
> Peter
> - who doesn't know vb3 but - unfortunately - knows vb6...

well see that was the catch....I got it and it still won't work
right....crashes all the time...won't let me load a character or a
deck....nothing

Further Reading

If you enjoyed reading about [OT] Dumpshock Site Software, you may also be interested in:

Disclaimer

These messages were posted a long time ago on a mailing list far, far away. The copyright to their contents probably lies with the original authors of the individual messages, but since they were published in an electronic forum that anyone could subscribe to, and the logs were available to subscribers and most likely non-subscribers as well, it's felt that re-publishing them here is a kind of public service.

Thwap!