|
Subscribers H/PC Guru Posts: | 5,289 |
Location: | United States | Status: | |
| Quote C:Amie - 2023-02-02 8:30 AM
Quote torch - 2023-02-02 2:58 PM
Correct, but I just have to add we probably need to do another round of testing for the arm vb runtime.
Because, the vb runtime full from last week worked on my 900 running 4.2 but when I pulled the cab last night, that one doesn’t work. So I think something happened in between the two?
Don’t do too much work yet because I didn’t use a control app. I used my test for hbomb which admittedly is one of the more problematic vb runtime programs (can’t get it to work on my ce6 x86).
The one I pulled last night installs correctly but doesn’t “associate” when I tried running hbomb That is item #7 on my list above
Yes I’m aware. I was merely following up that I believe it worked as of last week but something changed between then and now. |
|
| |
|
Administrator H/PC Oracle Posts: | 17,732 |
Location: | United Kingdom | Status: | |
| Quote I dunk for bananas - 2023-02-02 5:25 PM
This tells me that the .vb file isn't associated with it. Hmm, let me see Oh, oops my bad. I wrote it to HKLM not HKCR. Uninstall it and try again. |
|
| |
|
H/PC Elite Posts: | 574 |
Location: | Europe | Status: | |
| Still giving me the same error  |
|
| |
|
H/PC Elite Posts: | 574 |
Location: | Europe | Status: | |
| Works now! I had to add quotation marks in the shell\open\command path |
|
| |
|
Administrator H/PC Oracle Posts: | 17,732 |
Location: | United Kingdom | Status: | |
| Quote I dunk for bananas - 2023-02-02 6:53 PM
Works now! I had to add quotation marks in the shell\open\command path ah yes, good call. As you can probably tell, my mind is so fried with this, I'm making silly mistakes at this point.
So the answer would seem to be, yes, it can run from storage. Interesting.
Can you please check the windows folder and make sure they're are no remnant dll files from past installs? We wouldn't want it to be a fluke. |
|
| |
|
Subscribers H/PC Guru Posts: | 5,289 |
Location: | United States | Status: | |
| Is there anything you need me to help test with on x86 or is this mainly for the external storage? |
|
| |
|
Administrator H/PC Oracle Posts: | 17,732 |
Location: | United Kingdom | Status: | |
| Not yet. I'll try and go back to scheduled testing tomorrow and we'll fix the MP900.
If at some point you could please answer the couple of questions in my previous list. If you get the same error about VBCE2 and pvb before and after a file extension change then getting VBCE1 going on x86 is unlikely to happen. But we can look at that too.
For the time being though, it feels like all I've done for the last week is make pointless builds off the x86 runtime while needlessly rewriting cab maker to fix a bug that wasn't mine. So I'm a bit tired of it at the moment.
I also had to do a load of impromptu modding of the forum today to fix their (and Microsoft's ) bug. I don't want to look at a computer any not tonight  |
|
| |
|
Subscribers H/PC Guru Posts: | 5,289 |
Location: | United States | Status: | |
| Quote C:Amie - 2023-02-02 7:45 AM
Okay, so. Let's regroup here and test our understanding of where we are up to:
- I've been building presumably working 486 builds for 2 weeks now, but the forum has been boundary breaking them. CE 3.00 doesn't care, CE 6.03 does
- torch's CE 6 device doesn't have any registered error handlers for the Windows CE CAB installer, so its response on ANY error is to just exit? IDFB's CE 5 device is showing errors as is the MP790
- 486 build's won't work on IDFB's CE 5 device, but will work on torch's CE 6 device
- 686 builds will work on IDFB's CE 5 device but won't work on torch's CE 6 device
- CEF work on both of them, but that's because CEF will install on anything
- VBCE 2.0 is working on both x86's AND the MIPS MP790 CE 3.0
- VBCE 2.0 is NOT working on ARM MP900 CE 4.2
- All VBCE 2.0 icon issues are solved
- The last working VBCE build that attempted to register .PVB is erroring with a message that .PVB cannot run through the VBCE 2.0 runtime
- If you take the SAME .PVB and rename it to .VB, it works using the VBCE 2.0 runtime?
- What .PVB is our test app that works when being renamed to .VB?
Is that all correct and does it cover everything?
Sorry let me clarify.
When I say I test VBCE1.0, every single time I’d try leaving it .pvb but I’d also rename it .vb. Both were unsuccessful |
|
| |
|
H/PC Elite Posts: | 574 |
Location: | Europe | Status: | |
| |
|
| |
|
H/PC Elite Posts: | 574 |
Location: | Europe | Status: | |
| And I've fixed it! Looks like the keys to load up the DLLs of the runtime were missing
Does anyone know what all those keys are that are responsible for loading the DLLs? I don't really want to run regsvrce 15 times at each startup  Edited by I dunk for bananas 2023-02-02 10:35 PM
|
|
| |
|
Subscribers H/PC Guru Posts: | 5,289 |
Location: | United States | Status: | |
| I Can install it on my MobilePro 790 windows ce 3.0 MIPS? And send you my .reg file? Would that help you?
I can’t do it now but after work I can |
|
| |
|
H/PC Elite Posts: | 574 |
Location: | Europe | Status: | |
| I appreciate the offer though I think I'll just stick to using the regsvr way for now, it's quicker and the most reliable for now 
But god, regimp is beyond frustrating.
This is what's in the reg file:
@=""\Hard Disk\VBCE2\PVBLOAD.EXE" %0"
And this is what ends up in the actual key, which of course does not work, since there's an unnecessary extra pair of quotation marks:
""\Hard Disk\VBCE2\PVBLOAD.EXE" %0"
I've tried doubling the backslashes or removing them around the executable path, but that also doesn't work since then the system will just be looking for "\Hard"...
Removing the surrounding quotation marks doesn't work either.
Any ideas perhaps?  Edited by I dunk for bananas 2023-02-03 12:16 AM
|
|
| |
|
H/PC Elite Posts: | 574 |
Location: | Europe | Status: | |
| Fixed. The solution was to enclose it with 's
Now I have a persistent VB runtime!  Edited by I dunk for bananas 2023-02-03 12:38 AM
|
|
| |
|
Subscribers H/PC Guru Posts: | 5,289 |
Location: | United States | Status: | |
| Congrats, I dunk for bananas. Glad you got it sorted
C:Amie: Some follow ups
1-Did a hard reset, redownloaded VBCE-2.Full.HPC2000.arm.cab
^Runtime Installs Correctly; Tried with a previously known program to function on the MobilePro 900 CE 4.2 - doesn't associate, thus does not run
2-My MobilePro 700 running CE2.0 is aliveeee - I should be able to assist testing your runtime, as well as dumping its registry for pvb in the next few days. So I recommend halting any .pvb (VBCE1.0 ) experiments until you hear from me Edited by torch 2023-02-03 7:11 AM
|
|
| |
|
Administrator H/PC Oracle Posts: | 17,732 |
Location: | United Kingdom | Status: | |
| Quote I dunk for bananas - 2023-02-02 6:53 PM
Works now! I had to add quotation marks in the shell\open\command path
Here it is again, but with the quotation marks fixed |
|
| |
