VB Visual Basic Program on x86

Okay. I have removed PD9's file upload code for the main forum upload page and replaced it with my code from Elara (the one that is used everywhere else on the Site as well as on CAB Maker).

If I upload and then re-download files, I get the SAME hashes back

8697EDC0AE5AFA7E30FF2DA2032B9031CD556EC51728A3ECCD5F3E0DA94076F9
8697EDC0AE5AFA7E30FF2DA2032B9031CD556EC51728A3ECCD5F3E0DA94076F9

ARGHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH HHHHHHHHHHHHHHHHHHHHHHHHHHH HHHHHHHHHHHHHHHHHHHHHHHHHH HHHHHHHHHHHHHHHHHHHHH



All those builds, all that testing, all the wasted hours and it was a bug in someone else's code. I was starting to think I was going loopy.

So is there any issue creating cabs with x86 binaries but marking them CEF so it’s the lowest common denominator for both I dunk for bananas and myself v

It certainly looks that way, yes. Which is crazy. There is no way that your system is actually a 486 and not a 686. I mean, it just can't be given its age, surely

What is it, an AMD processor?

vendor_id : CentaurHauls
cpu family : 6
model : 13
model name : VIA Eden Processor 1000MHz
stepping : 0
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge cmov pat clflush acpi mmx fxsr sse sse2 tm nx pni est tm2 xtpr rng rng_en ace ace_en ace2 ace2_en phe phe_en pmm pmm_en

My system's CPU is a Celeron M apparently

LOL "cpu family : 6" i.e. a 686....

That is 100% a 686

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?

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

Edited by torch 2023-02-02 2:59 PM

Do you know if it's possible to install the runtime on a CF card (save for vbscript.dll I believe)? I'm assuming that it's possible with the right registry entries, though I'm uncertain what all the required registry entries are. After a fresh install there's definitely more registry additions than are listed in the cab extractor tool I use. Do we know what all those entries are?

That is item #7 on my list above

No clue, but here is a .VB only build that will install to
\Storage Card\VBCE2

It MUST be that path or it won't work.

vbscript.dll goes to \Windows, everything else goes to the Storage Card

Uninstall all previous versions fist.

It's \Hard Disk for me, would it be possible to change it..?

Attached

This tells me that the .vb file isn't associated with it. Hmm, let me see