60 replies to this topic

[MedEvil]

Path not found sounds stupid for the exe.
I have a long list of errors i would expect to be more likely with that kind of program.

Besides checking with filemon, i have no new idea.



PS: Bad news the error message seems not to come from the exe or the dll directly. None has any matching error messages.

[allanf]

You can see the error message in post #29. It looks like ViStart.... maybe not.

ViSplore requires a System Tray. That might be the first consideration. xoblite's is a bit flaky at times. bbLean's is OK. and others are fine. Do you happen to know of standalone TaskTray and SystemTrays, or just use any old shell?

Damn! Trying to get the ViStart started then try out the Orb. BTW, what do they do? ... ...

[MedEvil]

You can see the error message in post #29. It looks like ViStart.... maybe not.

I really have to pay more attention. It clearly says run-time error. So it's an error encountered 'in' the VB library.

ViSplore requires a System Tray. That might be the first consideration. xoblite's is a bit flaky at times. bbLean's is OK. and others are fine. Do you happen to know of standalone TaskTray and SystemTrays, or just use any old shell?

I don't didn't care much for looks, so it's eighter explorer shell or explorer shell for me.

I know, you've said you already done a dependency scan. But since i'm fresh out of ideas ...
 ViStart.depend.txt   5.49KB   299 downloads

I think at this point the author is really your best bet.
Tell him about the error and ask him to give you a list of used/required folders or required Folder related variables and registry keys.

While you're at it, tell him that you want to run ViOrb and ViStart in an environment without explorer shell.
Wait for the first shock to settle, then tell him it's not a joke!

[allanf]

[quote name='MedEvil' date='Feb 18 2009, 11:05 AM' post='59664']
I see in the FAQs for ViStart that the Start Menu should be set to XP rather than Classic as a requirement for installing ViStart. It's a bit hard to set in PE.

There were also some suggestions in the forums that ViStart doesn't work in a roaming profile, only local. The error message was similar but not identical to the one I have.

I can't draw any conclusions about what's actually wrong, and would have little idea about how to fix it.

I've tried it with four different shells - xoblite, bbLean emrgeDesktop and BSExplorer. (The latter has at least a startbutton and menu.) It's always the same error with ViStart.

The author responded to my posts but was concerned about ViSplore windows not having borders in WinPE 3.0 (Win7). My issue ATM is ViStart in WinPE2.1.

I'll try to do a script for my project, going as far as I have got, and post it in the hope that someone else might like to figure it out. Need to brush up on some techniques for exracting a registry key, ammending the .reg and saving it to another key - all at boot-time.

I feel it's a shame to have only a working ViSplore without its siblings - ViStart and ViOrb. I wonder how long til there's a ViShell.

That's about it.

Thanks again, MedEvil, for finding it and the help.

[MedEvil]

I see in the FAQs for ViStart that the Start Menu should be set to XP rather than Classic as a requirement for installing ViStart. It's a bit hard to set in PE.

How can you underestimate me like this?
The log for the install, the one i told you could easily be converted to a reg file, contains of course this setting, because i knew you wouldn't have it.

[allanf]

How can you underestimate me like this?
The log for the install, the one i told you could easily be converted to a reg file, contains of course this setting, because i knew you wouldn't have it.

As I (mis)understood it, the log contained a record of changes made during the installation.

Which key contains the pre-set (before installation) XP-style startmenu?

[MedEvil]

As I (mis)understood it, the log contained a record of changes made during the installation.

Which key contains the pre-set (before installation) XP-style startmenu?

You understood right. The log contains the changes done during install. But i switched to classic start menu before taking the first snapshot.
Then changed back to default start menu and installed ViStart. Exited ViStart and took the second snapshot.

All the registry keys listed as new should be from ViStart. The one lited as just changed should be from the start menu.

[allanf]

All the registry keys listed as new should be from ViStart. The one lited as just changed should be from the start menu.

No such listings for reg keys. It does tell me how many were added or modified though.

I can't run it as a .reg because of all your personal settings.

Any other ideas?

[MedEvil]

No such listings for reg keys. It does tell me how many were added or modified though.

Ok, then not new and changed but added and modified. Same difference!
And which one do we use? Hmm, let's see maybe the one saying Software\Microsoft\Windows\CurrentVersion\Explorer\"ShellState" ?

Here is the exact value:
RegWrite,HKLM,0x3,"Tmp_default\Software\Microsoft\Windows\CurrentVersion\Explorer","ShellState","24","00","00","00","31","28","00","00","00","00","00","00","00","00","00","00","00","00","00","00","01","00","00","00","0d","00","00","00","00","00","00","00","%DefaultStartMenu%","00","00","00"
Now replace %DefaultStartMenu% with 02

I can't run it as a .reg because of all your personal settings.

I told you before, that you should adopt the paths to your needs.

Any other ideas?

Don't give me ideas!

[allanf]

Ok, then not new and changed but added and modified. Same difference!

I didn't mean to sound rude. Just meant to say that the keys are not listed as new (added) or changed (modified), so it was abit hard to tell whcih were which..
Though, I am a bit frustrated and nearly ready pack this. The only positive outcome is the creation of a ViStart folder in UserProfile sub-directory rather than out in the cold on x:\.

And which one do we use? Hmm, let's see maybe the one saying Software\Microsoft\Windows\CurrentVersion\Explorer\"ShellState" ?

What;s your tone?

I'll try to set that key before installing/starting ViStart.

BTW adopt not equal to adapt! Both could be use in the given context, but with slightly different meanings.

Regards

[MedEvil]

I didn't mean to sound rude. Just meant to say that the keys are not listed as new (added) or changed (modified), so it was abit hard to tell whcih were which..
Though, I am a bit frustrated and nearly ready pack this. The only positive outcome is the creation of a ViStart folder in UserProfile sub-directory rather than out in the cold on x:\.

Sorry that i misread you.
But i don't get your problem. With the registry entries in place ViStart should might still refuse to work but the error message should disappear or at least change.
You can not have all dependencies solved, all paths created and all registry settings in place and still get a path error! That's just not possible!!!

What;s your tone?

I'm getting really frustrated.
I told you that ViStart will not start without the Registry entries a bunch of posts before and now you tell me that you haven't yet used them!

I'll try to set that key before installing/starting ViStart.

The key will not solve any error messages. When it is not properly set, Vistart will just not show up even though it's running.

BTW adopt not equal to adapt! Both could be use in the given context, but with slightly different meanings.

Sorry make this error a lot, i mean adapt.


You can try to use an XP install in a VM.
Install ViOrb and ViStart. When you know that they work, you start replacing the shell.
They still work? Start throwing out files that are not in you project till they fail.
They do not fail even after all files have been thrown out? Start throwing out registry keys.

I personaly, find the add approach we've done so far, easier, but maybe this works better for you.