Kilotecs Software Corner

Oh oh oh... got a problem.

my new app would not start on my Jornada. It ran fine on the emulator. On the Jornada there was an hourglass of death.
Suddenly not a single program that was programmed with eVB worked anymore.
Throw everything down and reinstall the individual apps. But nothing can be started anymore.
Constantly the message: There is no program assigned to this file.
So I shot myself something. It is no longer possible to start a program that was installed via .CAB.
The CAB file provides everything that is necessary at runtime. I do not understand that.

You need to hard reset the device / delete all data once you backed up what you needed.

-Your software includes the runtimes for CE2.11 only. You can’t install it on a different version or it will break and not work.

Do this:
-Hard reset
-install this “hpc2000” arm version from here https://www.hpcfactor.com/scl/1982/Microsoft_Corporation/Visual_Basi...
-install your cabs but DO NOT let it install the runtime

The problem is: all my apps work fine.
Today I installed a new one to test it, as I have already done umpteen times. Only this time the app just won't start, it gets stuck with the hourglass. After a soft reset, the other apps no longer work either. Only when I install a new one again does everything work again. Until I just launch my newest app, Hourglass of Death and everything falls apart. Something is wrong with the new app, although I haven't done anything else with it. I also never reinstall the runtimes. I said yes: everything has always worked. To date with the new app

Email me that one and I’ll try on my three devices.

Or...don't use your .cab file, try executing the "raw" .vb file and see if that works instead?
That's how I have to execute your programs on x86

First I thought it freezes because of some savesetting routines in the registry. But I cut all out.
It is really frustrating. I don't know how to fix this issure.
I will send u the CAB...

You have mail torch.

As I wrote you in that mail: I haven't changed anything. Built the CAB like the other apps. Installed the app like the other ones but than everything collapsed.
The VB icons of my apps are gone. After installing one of the apps again everything works fine 'til I start the problem app again.

Edit: on the emulator, everything works fine

Edited by Citgo 2023-02-06 6:38 PM

There's something different about this .vb. I didn't do full testing on my other devices, but it doesn't work on my x86 device.
I get an error about pvbload.exe
Maybe you need the ADO runtime installed?

Edited by torch 2023-02-06 6:42 PM

The funny thing is: I just copied the folder of another finished app and rewrote this app. So, nothing changed or made new. And no matter how many times I recreate the CAB file, this error every time.

Okay, do this:
Hard reset the device. install the runtime I linked earlier. then check your email and just copy the zip file I made to the device and just try to run the plain .vb file and let me know what happens.

*crrryyyy* hard reset?
I have no chance to backup my PIM stuff. Or can I access these tasks, calendar, contacts, etc. files in order to copy them to my CF??

Even if that work what would that mean for future projects? I mean...the user should only install tha CAB instead of copy here, copy there...you know what I mean?
So there must be another solution because all other stuff works fine. Argh...I dont know

Okay do this instead.
Don't hard reset
-Reinstall that runtime I linked
-Soft reset
-Try a VB program that you know works
-^If it works, then try the extracted zip file I made for you

I know that, I want to figure out what is wrong with this new program and then we can go back and figure out how to fix up the cabs
There is something different about this one

Ok...first of all, I'm enjoying my bath now
Then I will have a look. Shhh: I cant download right now from the SCL. But I will subscribe the next days...

Then, maybe tomorrow (it is couch+wife+tv time in Germany right now) I will make a new, almost empty app and see what happens when I install it. If everything works then I will have a deeper look to my new app. But... there was one time today where the app runs on my Jornada.
And I thought that the problem was solved. So... I guess starting the app kills my runtimes