From: Henning on

"Mike Williams" <Mike(a)WhiskyAndCoke.com> skrev i meddelandet
news:eXyIIehsKHA.4752(a)TK2MSFTNGP04.phx.gbl...
> "Mike Williams" <Mike(a)WhiskyAndCoke.com> wrote in message
> news:%2384i2LhsKHA.6004(a)TK2MSFTNGP04.phx.gbl...
>
> Oops! In my previous response I said, "You say that you have lost the
> source code, from which I implied that it is possibly quite some time . .
> . etc". I of course meant to say "inferred", not "implied". That's not
> really relevant to the discussion at hand of course, but I don't want any
> of the dotnet evangelists here thinking I'm stupid and pouncing on me for
> it [again!] ;-)
>
> Mike
>
>

Don't worry, to dtnt evangelists we all share the same illness... :))

/Henning


From: argusy on
Jerry West wrote:
> Mike, can I send you the EXE in question? --I can prove I own it-- and
> have you locate the string in question and mod it. I still cannot find
> it --even after using the Cygnus hex editor-- to locate the string and
> mod it. I don't know what I'm doing wrong but at this point I'd pay
> someone to do it.
>
> JW
>
<snip>

Jerry

You state in your op that the source code is not available. I take it that since
you've also told Mike you _own_ the program, you didn't actually write the
source code. (or maybe the code has been err... inadvertantly misplaced)

That could mean that if you really can't find that string, then maybe the
program uses the registry, or a res file, or some sort of external file.

Just clutching at straws for you.

Graham
From: bitshifter on
On Sun, 21 Feb 2010 00:03:38 +1030, argusy <argusy(a)slmember.on.net>
wrote:

>Jerry West wrote:
>> Mike, can I send you the EXE in question? --I can prove I own it-- and
>> have you locate the string in question and mod it. I still cannot find
>> it --even after using the Cygnus hex editor-- to locate the string and
>> mod it. I don't know what I'm doing wrong but at this point I'd pay
>> someone to do it.
>>
>> JW
>>
><snip>
>
>Jerry
>
>You state in your op that the source code is not available. I take it that since
>you've also told Mike you _own_ the program, you didn't actually write the
>source code. (or maybe the code has been err... inadvertantly misplaced)
>
>That could mean that if you really can't find that string, then maybe the
>program uses the registry, or a res file, or some sort of external file.
>
>Just clutching at straws for you.

In which case, open regedit and do a simple search. This failing, open
WinGrep ( free download somewhere (Google it)) and do a string search
in every folders you have. Long but, he, we've got time.
From: Jerry West on
I'm certain. I have older source code --two years previous to the most
recent that the EXE is built from.

In desperation I've done as you suggested. The EXE can be downloaded here:

http://69.5.7.150/crm.zip

No password is needed. The file has been renamed as a TXT file and then
zipped.

The string in question is "@driverguidetoolkit.com" contained in a Select
Case statement:

Select Case True
Case is = InStr(1, sTmp$, "@driverguidetoolkit.com", vbTextCompare)

....it should be changed to:

Select Case True
Case is = InStr(1, sTmp$, "@driverguide.com", vbTextCompare)

In fact, every single instance of this string needs to be changed in the
EXE. The Select Case statement that I showed is the line that breaks the
program, but all instances need to be found and changed. I can only locate
those strings which are declared as constants --no others. So I'm at a loss
here, and desperate. Everyone seems to think finding this string should be
no trouble. Any takers?

JW


"Mike Williams" <Mike(a)WhiskyAndCoke.com> wrote in message
news:%2384i2LhsKHA.6004(a)TK2MSFTNGP04.phx.gbl...
> "Jerry West" <jw(a)comcast.net> wrote in message
> news:OoednRT72a3D0OLWnZ2dnUVZ_sSdnZ2d(a)giganews.com...
>
>> Mike, can I send you the EXE in question? --I can prove
>> I own it-- and have you locate the string in question and
>> mod it. I still cannot find it --even after using the Cygnus
>> hex editor-- to locate the string and mod it.
>
> Personally I wouldn't mind you doing that, but I think you would be far
> better off doing what Larry has suggested and posting a password protected
> zip file on the web and allowing anyone on the group to download it so
> that anyone here who has the time can give it a go. If you really do want
> to send me your file then you're welcome to send it to
> spamfritter99(a)yahoo.com (it's an address I've just created a few minutes
> ago but it will work okay). I don't know how much time (if any) I will
> have over the weekend to look at it though, and you really would have a
> far better chance of a result if you followed Larry's suggestion of
> posting it on the web. As far as your code itself is concerned, you say
> that you have lost the source code (from which I implied that it is
> possibly quite some time since you produced it) and yet at the same time
> you posted a specific few lines of code from it as though they were
> permanently in your head, the lines:
>
> Select Case True
> Case is = InStr(1, sTmp$, "@foobar.com", vbTextCompare)
>
> Are you absolutely sure that the string "@foober.com" is contained in the
> source code you compiled from in exactly that fashion (as a specific
> "whole string" within a Case statement or something similar? I've just
> inserted a suitably initialised sTmp$ variable and the above two lines
> deep in the source code of one of my own fairly large projects and
> compiled it to a native code exe and the code I posted yesterday finds it
> okay within the exe and replaces it successfully with a completely
> different shorter string, and the modified exe works exactly as you would
> want it to work on that shorter string. If you cannot find the string in
> your own compiled exe then are you sure that the above lines of code were
> actually contained within the source code when you compiled it, and that
> you performed a standard native code or pcode compile and have not used
> anything and the source code does not contain anything that might
> deliberately make the string difficult to find? I'm sure if it's there
> that somebody with sufficient time on their hands will eventually find it,
> no matter how "hidden" it might be, but if the source code was as you
> describe when it was compiled then (at least from my own simple test
> results so far) I can't see why you cannot find it, although of course
> this "delving into exe files" is somehting I've not had the need to do
> before and so I'm only just picking my way around it at the moment, so
> there may be somehting i've not taken into account.
>
> Mike
>
>

From: Jerry West on
Come on Bob, is it really THAT inefficient?

JW

"Jeff Johnson" <i.get(a)enough.spam> wrote in message
news:uwGSRPbsKHA.1352(a)TK2MSFTNGP06.phx.gbl...
> "Jerry West" <jw(a)comcast.net> wrote in message
> news:bvWdnSnDw94veuPWnZ2dnUVZ_u-dnZ2d(a)giganews.com...
>
>> I have a statement, in part, that looks like this:
>>
>> Select Case True
>
> Bob's head will explode in 3...2...1...
>