A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Windows 10 » Windows 10 Help Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Win 10-64bit + VB6 + National PCI-GPIB card?



 
 
Thread Tools Rate Thread Display Modes
  #16  
Old February 2nd 18, 11:44 PM posted to alt.comp.os.windows-10
VanguardLH[_2_]
external usenet poster
 
Posts: 10,881
Default Win 10-64bit + VB6 + National PCI-GPIB card?

mike wrote:

VanguardLH wrote:

Still no explicit reason given as to why you need to move away from a
working setup using an older version of Windows to a non-working, flaky,
or unknown (from unknown sources) setup with a new version of Windows.


Lighten up!! It's a hobby.


So the old hardware is not critical. Keep playing with trying to fit a
square peg into a round hole. Tis possible you'll find a working jigsaw
to make the round hole big enough for the square peg to fit into it.

Making win10 and Linux yield to my needs is something to do. It's
progress. If you think you'll never have need for win10, you won't be
doing much in the future.


I have an experiment Windows 10 host at home but not very often because
there's no bang-for-the-buck for me to spend time on it. I use and have
deployed Windows 10 at work in our alpha test lab. We also have *NIX
hosts at work because Windows is not appropriate for their tasks.
Windows 10 is not an appropriate OS for all applications. I need a task
to get done, I find what software is available, and then pick the OS to
achieve the task, not ass backwards by getting the OS and then see what
happens to run on it.

My motives are mine. They don't have to agree with yours.


Zim zim ala bim, the spirits are about to speak. Uh, what, oh, they say
they don't know your motives because you never mentioned them, like you
are trying to cull for help on something that is unimportant. Yep, I've
got other better things to do than waste on triviality. I don't bother
helping a user that wants to change the desktop's background, either.

Hope you find a solution with your hobby hardware playing. Sometimes we
do things that are challenging, not because they are logical. "The
harder the conflict, the more glorious the triumph" (Thomas Paine).
Humans thrive on conflict hence the use of general-purpose computers.
Ads
  #17  
Old February 3rd 18, 12:00 AM posted to alt.comp.os.windows-10
mike[_10_]
external usenet poster
 
Posts: 1,073
Default Win 10-64bit + VB6 + National PCI-GPIB card?

On 2/2/2018 5:23 AM, Paul wrote:
mike wrote:
On 2/1/2018 1:39 PM, VanguardLH wrote:
Still no explicit reason given as to why you need to move away from a
working setup using an older version of Windows to a non-working, flaky,
or unknown (from unknown sources) setup with a new version of Windows.
What does Windows 10 give you that is critical to your application? Is
the OS more important than what appears to be critical hardware for
whatever is your application of that hardware? Which is more critical:
the hardware, the software, or the OS? So far, the only inferred reason
you think you need to "transcend" to a newer OS is simply because a new
one exists (exemplified by consumers well-trained by the "newer is
better" marketing mantra).


Lighten up!! It's a hobby.
Making win10 and Linux yield to my needs is something to do.
It's progress.
If you think you'll never have need for win10, you won't be doing much
in the future. More and more applications are dropping support for
32bit operating systems. Don't need it today, but you will tomorrow.

My motives are mine. They don't have to agree with yours.
Helping me is your choice...do or don't.

Latest National GPIB drivers seem to be working just fine using the
national direct access tools.

The VB6 problems seem to revolve around 32:64bit issues.
DLLs seem to get randomly distributed around system32, syswow64 and
system
directories. It doesn't match up, so the app can't find what it needs.
Still working on that. I gave up on the new VB6 install thru inosetup.
Simple programs work, but the package distribution tools don't.
Full VS6 install is better, but still no cigar...yet.

One thing I still can't get my head around is that I can make an install
file on a fully functional 32-bit win7 system, and it still won't
install properly
on win10-64. It gets stuffed into program files(x86), so it knows it's
a 32-bit program. The files it can't find are right there in the
directory.
I even repackaged the app to put all the system support files into the
app directory. Still no go.


I'm able to get very simple GUI VB6 programs to run in linux/wine,
but hardware access is an issue. There's a recent update to linux-gpib
so all is not lost yet.


Do they need to be registered ?

https://en.wikipedia.org/wiki/Regsvr32


I tried that. Don't remember the exact error message, but the gist
was "It failed to do that."

My program has a .cls file that translates between VB6 and the system
calls needed to access the National Instruments driver.
I copied it from an example almost two decades ago and modified it
to suit. I need to remember how that works and see if there's anything
in there that I can do.

As I write this, I'm realizing that maybe there's some 16-bit stuff
in there and that's why it won't work on a 64-bit OS.
This project started in win95 with VB3. I kept upgrading the OS
and VB
and it kept working until 64-bit OS. Hmmmm!

The maddening thing is that the VB6 IDE starts execution, then fails
with the message that it can't find a file and maybe I should reinstall it.
Usually, the IDE drops back into the program listing at the point
of the error, but that didn't happen here.

Sorry, I didn't write the file name anywhere I can find.

Problem is that that file is nowhere to be found.
Not anywhere on the 32-bit system that works fine.
Not anywhere on the 64-bit system that doesn't work.
Not anywhere in the National instruments downloads.
Not anywhere in the VB6 files.
A google search got three (THREE!) hits.
All from the same place, in German. The translation gave me zero
insight.

I haven't a clue as to when something should be registered

Nor do I, but I think it gets really complicated when you have a mixture
of bitness. You have program files, program files(x86), three versions
of system. I have near zero experience with the depths of 64-bit windows.
and when it will be resolved via $PATH or something. My little
programs here have never been complicated enough to need it.

Paul

My epiphany about lurking 16-bit baggage is worth pursuing. It fits
the overall symptoms.

I don't look forward to being forced to vb.net.
Last I looked at it, I spent WAY more time defining
objects than I did writing the three lines of code needed to
do something. Might as well go all the way to C.
 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 09:51 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.