VB Visual Basic Program on x86

Good to know thanks. I am inclined to leave it as it rather than re-write it to change the copy options? Perhaps worth a note in the install instructions though.

Try this on MIPS with a .pvb

Please take any existing off first or hard reset

And here is ADO, so PoS should would once it and VBCE 2 are installed.

If it does, I'll build ADO for all platforms.

Doesn't complete-hangs at "Creating Registry Entries" on CE3.0 MIPS MobilePro 790 (I did replace .dll install)
VBCE1.0 just shows hourglass and doesn't execute

I think PoS requires more than just that because that combo doesn't work to load PoS. I suspect dll issues. Is there a simpler program that uses ADO?

Oops, sorry, I meant PoQuick, not PoS.

Possibly because I used the 2.11 runtime not the 3.00.

Two version attached, both CE3 mips, one with an extra regsrv and one without.

Gotcha. When I get off work in 11 hours I’ll do that and let you know

Optimistically, I'll be asleep at 2am

Microsoft.VBCE2.0RuntimeforCE3.0.MIPS4K-no-pvbrt-reg - > installs correctly, VBCE1.0 doesn't work , VBCE2.0 does work
Microsoft.VBCE2.0RuntimeforCE3.0.MIPS4K-pvbrt-reg -> Hangs at the very end for install, had to soft reset to get it out of that, VBCE1.0 doesn't work, but hourglass shows like it wants to then just keeps hanging, VBCE2.0 works
Both show icons finally for PVB progs after soft reset..so progress ?

POQuick still doesn't work on x86, hangs at 30%


Edited by torch 2023-02-05 7:49 AM




Attachments
----------------
poquickx86.reg (998KB - 0 downloads)
cab no pvbrt.reg (186KB - 0 downloads)
cabpvrtreg.reg (193KB - 0 downloads)

30% of what sorry? Is there a loading screen with a % indicator?

I think that I agree with the existing consensus that it won't be possible to co-exist both runtimes together. The only thing that we have not tried at this point is running them as a shadow registration. You will find both of those attached for MIPS.

Please install VBCE 2.0 separately >first< then install 1.0 NO-REF and test PVB. The hard reset, install 2.0 then install 1.0 SHADOW-REF and then test.

I expect NO-REF to break everything and SHADOW not to work though.

Unchanged.

Let's try this idea then:
Forget about having them co-exist.
What about building a runtime that completely overwrites VBCE2.0 if it's baked in ROM, and it ONLY lets you use VBCE1.0 programs. Then 2.11, 3.0 + users have a way to use those programs?

The difficulty will be in un-registering 2.0 first. The my knowledge the Windows CE CAB installer doesn't have the ability to delete from the registry, you have to write a CPU specific DLL to do it

We're clearly in a broader spectrum of discussion than just CE 6 and newer devices (where this thread started), so . . .

Moved to Handheld PC General Discussion

Ok I have an idea. Do you want to test x86 CEVB1.0 then?
I’m the perfect candidate because there’s no vb files installed in rom.

There isn't an x86 version of 1.0. Only MIPS3k, MIPS4k, SH3 and x86em.