Re: VB program conversion from Windows 95 to Windows XP
- From: "Rainer Koenig" <rainer.koenig@xxxxxxxxxx>
- Date: Fri, 12 Aug 2005 09:32:44 -0600
I followed your suggestion and got into the old closet with a windows 95
system in it that could recompile my program. It still does compile and
built the same executable.
Then I tried to isolate the hundreds of possible errors that all funnel into
one. Executing this version of the 95 executable on XP led me to the same
problem as the compile on XP. It died in the initialization of the ADO
data-base, so I am back to square one.
Any further suggestions?
"J French" <erewhon@xxxxxxxxxx> wrote in message
news:42fb21f9.7191930@xxxxxxxxxxxxxxxxxxxxxxx
> On Wed, 10 Aug 2005 11:18:49 -0600, "Rainer Koenig"
> <rainer.koenig@xxxxxxxxxx> wrote:
>
>>regarding the first comment (get the existing code complied under Win95
>>working under XP): I believe that is exactly what I'm trying to do.
>
> Sorry - I did not make myself clear
> - dust off your Win95 setup and compile on that
>
>>regarding the second comment (you are changing to many variables at the
>>same
>>time.): I do not know how to reduce the number of changes in this
>>process.
>>[I simply moved working source code from a windows 95 release to a windows
>>xp system using the same old VB interpreter/compiler]. I have resisted
>>upgrading the interpreter/compiler to SP5.
>
> Moving platforms is a bitch
> - only do it when you do /not/ have a problem
>
>>regarding the question (How are you reading the .TXT files ?):
>> Open Dir1 & "\" & InputFile For Binary As #1
>>followed by a series of "get #1" statements
>
> FreeFile - but that is not relevant now
>
>>finally regarding the last question (what goes wrong ?):
>> the windows 95 executable is geared to interpret a logging file
>>generated by our machine with a very specific format. The same (not
>>recompiled) executable under some versions of windows xp (SP2) comes back
>>with a format error, i.e. the specific format is violated. So under those
>>versions of XP (including my desk top PC and the field technicians
>>lap-tops)
>>extra characters or missing characters are present. The only way I know
>>of
>>to isolate this problem is to recompile and track down what the problem is
>>using debug info, but I cannot recompile.
>
> Recompile under Win95 on your old platform
>
> Add in logging, trace everything round the hooky area
>
> You will find that the format of the file that you are reading has
> changed.
>
> Or possibly that there are some 're-defined' API calls
>
> You need to set up an XP testbed that fails (as reported by engineers)
> Then on a Win95 machine produce a self diagnosing variation of your
> established App which you put on a floppy and run on the XP box
>
> It is easy to give good advice
> - however I've been in the same situation
> - don't panic, trash the XP development machine
> - locate the problem with logs and probably Err.LastDllError
> - when it is fixed and running soundly for 28 days, then set up a new
> parallel XP machine
>
> Panic upgrades create panic.
.
- Follow-Ups:
- Re: VB program conversion from Windows 95 to Windows XP
- From: J French
- Re: VB program conversion from Windows 95 to Windows XP
- References:
- VB program conversion from Windows 95 to Windows XP
- From: Rainer Koenig
- Re: VB program conversion from Windows 95 to Windows XP
- From: Someone
- Re: VB program conversion from Windows 95 to Windows XP
- From: Rainer Koenig
- Re: VB program conversion from Windows 95 to Windows XP
- From: J French
- Re: VB program conversion from Windows 95 to Windows XP
- From: Rainer Koenig
- Re: VB program conversion from Windows 95 to Windows XP
- From: J French
- VB program conversion from Windows 95 to Windows XP
- Prev by Date: Re: context help OT kind of
- Next by Date: need help with a sql connection error in vb .net project
- Previous by thread: Re: VB program conversion from Windows 95 to Windows XP
- Next by thread: Re: VB program conversion from Windows 95 to Windows XP
- Index(es):
Relevant Pages
|