VB Visual Basic Program on x86

Still disappears (did hard reset before trying)

That's... unexpected.

Still?

Unchanged.
Can you give me the .reg file? Maybe I can import it manually in PHM Regedit? (are .reg files universal because I can't get TRE on this)
Like make your next cab the files/dll register

and then give me the .reg file manually?

So not %... let's try the commas?

Unchanged

Without the file handler?

This is all it is currently trying to do, nothing else:

[HKEY_CLASSES_ROOT\.pvb]
@="PVB.ProjectRun"

[HKEY_CLASSES_ROOT\PVB.ProjectRun]
@="VBCE Project File"

[HKEY_CLASSES_ROOT\PVB.ProjectRun\DefaultIcon]
@="\\Windows\\pvbhost2.dll,-2"

[HKEY_CLASSES_ROOT\PVB.ProjectRun\shell]

[HKEY_CLASSES_ROOT\PVB.ProjectRun\shell\Open]

[HKEY_CLASSES_ROOT\PVB.ProjectRun\shell\Open\command]
@="\\Windows\\pvbload.exe %1"

Installs correctly
VBCE2.0 does not work

So it is literally crashing because we are trying to add:
[HKEY_CLASSES_ROOT\.pvb]
@="PVB.ProjectRun"

That's it!

Here is the command to add the .vb, which works fine


Here is the command to add the .pvb, which does not work


You tell me why it won't work lol

Okay, I'll play with this tonight or tomorrow. About to head into work.
Thanks for your help!

Here it is again, but the .pvb line is the last instruction in the set.

Also one with just .vb and .pvb lines and nadda else.

Right you are, thanks for sharing a frustrating afternoon on this. I'm completely baffled! It makes zero sense. It's not a fault in CABMaker, or the Cab zipper. It looks like it's x86 CE's cab installer.

Have a good afternoon yourself

Microsoft.VBCE2.0RuntimeforCE3.0.486.cab - > Disappears
Microsoft.VBCE2.0RuntimeforCE3.0.486-just file ext.cab - > Installs correctly, VBCE2.0 doesn't work

VB Runtime doesn't work on my MobilePro 900
But yes, we'll work on one thing at a time but it was working before

I was thinking about this all night. It's seemingly baffling as to why it works on the 790 but not on x86. The different CE version is the prime suspect.

My thought last night was that it could be an encoding issue in the source. For some reason all the .reg files you've sent - and from which I've built the manual regsrv - we're UTF16. I'm wondering if there's a corrupt character encode being forwarded somewhere.

The idea is sensible, but for the fact the 790 should be breaking too.

It also doesn't explain why the regsrv on the x86 just won't work, while on MIPS they're fine.

Very frustrating!