VB Visual Basic Program on x86

Is there a magic trick to get the VB runtime to install for x86?
(I have the HP t5540 Client running ce 6)

It looks like it was able to do it before as multiple vb programs are on the x86 software list

I was able to get the runtime installed but nothing happens when I try to launch a vb prog

Edited by torch 2023-01-13 3:08 PM

I was having the exact same issue with x86 CE5. I was able to get programs semi-running (though nonfunctional with tons of error messages) if I manually tried to register the VB DLL files

What program did you use to register the dll files? I've never done that before

You should be able to use regsvrce.exe in your Windows directory!

Thank you. I tried it in following format
-open command prompt
-typed regsvrce.exe /example.dll

Then I get error of Load Library Example.dll failed get last error returns 7e

Remove the slash, it should just be "regsvrce example.dll"
Clearly on previous CE versions this was done automatically. I'm confused as to why on CE 5 and later we have to manually register these, and even then, VB programs don't run properly

Edited by I dunk for bananas 2023-01-13 6:36 PM

Thank you. That worked. I was able to register all of them except for vbrmon.dll because I get a dll register server entry point error
It says dll register server may not be exported or a corrupt version of vbrmon.dll may be in memory consider using pview to detect and remove it

Now .vb programs have an icon displayed but they still don’t run. I get an “you must open the program associated with it first”

Then when I try and run pvbload exe it just says cannot open program file.

Is there an mfc or other ce3.0 dependency im missing ?

in the registry, have a look in HKCR to see what the .vb handler is set to, then compare it to your MobilePro's

Oh and keep a list of the DLL's that need or do not need resvr as we can use CAB Maker to make a Runtime installer for x86.

What would the path of the key be?

Also with the thin clients does this mean I have to reinstall / redo this every reboot?

HKCR/vb

Correction: HKCR/.vb

I've found that pvbdecl.dll, pvbform2.dll, pvbhost2.dll, vbscript.dll, and each of the object controls (MSCE*.dll) need to be registered.

Good question about whether it has to be redone each time. I don't know if those thin clients flush their internal registries. Quick way to find out would be to create a registry key and then shut down and restart to see if the key still shows up. If not, using Total Commander to copy the registry keys (or HKCR as a whole, and HKCR and HKLM while you're at it to save all the other settings) over to whatever external media you're inserting in the device could make the restore process easier. (I find this is much faster than using a registry editor.)

Okay I have a weird cocktail that worked
I dunk for bananas:
install this first
https://www.hpcfactor.com/scl/64/Mastersoft/PoQuick_Money_Profession...
Then install this x86 full runtime
https://www.hpcfactor.com/scl/327/Microsoft_Corporation/Visual_Basic...

Now I can get vb programs running ! Well some of them.
Also, Citgo’s programs work now too

Edit: so theoretically if I extract both of those cab files we can combine them into one and create an x86 runtime that should work. (Obviously excluding the vb program itself )

Edited by torch 2023-01-21 8:08 AM

This request is now the same as https://www.hpcfactor.com/forums/forums/thread-view.asp?tid=20637 except it has x86 in the title.

Lets fix it over there and deal with this properly for all architectures.

Understood, we can work on one issue at a time, but they are three separate issues
-PocketC on x86
-Visual Basic Runtime on x86
-Pocket Visual Basic Runtime on HPC2000 MIPS
So we'll work on Pocket Visual Basic Runtime on HPC2000 MIPS first

But based on what I dunk for bananas said, we may not have a way to make a universal cab installer for x86. Perhaps just a CESD on how to attempt to do it manually

Edited by torch 2023-01-21 4:21 PM