Microsoft Small Basic - App-V 5.0 Crashes on launch

[J_Worth]

Hello everyone,

 

Been asked to deploy Microsoft Small Basic out to our IT Suite computers. We use App-V for all our software deployment. However, I have packaged the software into an App-V 5.0 SP3 Package but when testing it, Small Basic continually crashes during launch, at the splash screen.

 

I have tried tweaking various settings in the Sequencer, to no avail.

 

Was wondering if anyone else has had any success with getting Small Basic App-V'd?

 

Any help much appreciated.

[round2it]

Probably not an app v issue

I spent ages on this.

smallbasic when launched it just crashes.

Tried dot net upgrades

Vb runtimes everything i could think of it was not worth the time i spent on it

I had to reimage a couple of machines could not get it to work sorry no help

Edited September 2, 2015 by round2it

[Arthur]

We use App-V for all our software deployment.

It might be worth trying the App-V 5.1 sequencer, especially if you haven't installed any of the post-SP3 hotfixes for v5.0.

[J_Worth]

Tried packaging it using the App-V 5.1 Sequencer and Client to no avail.

 

Guess it's going to have to be deployed and installed virtually. There's probably a really quick fix, but I can't figure out.

 

It's annoying because its just a small application and would be really useful if it could be deployed using App-V. Maybe it has some hardcoded paths and when running in the App-V it breaks it...

 

At least, it's not an urgent thing to get installed, so I might have another go again with it.

 

If anyone has any bright ideas, please let me know and if I do figure it out, I'll post the solution on this thread.

 

Thanks again!

[J_Worth]

Tried packaging it using the App-V 5.1 Sequencer and Client to no avail.

 

Guess it's going to have to be deployed and installed virtually. There's probably a really quick fix, but I can't figure out.

 

It's annoying because its just a small application and would be really useful if it could be deployed using App-V. Maybe it has some hardcoded paths and when running in the App-V it breaks it...

 

At least, it's not an urgent thing to get installed, so I might have another go again with it.

 

If anyone has any bright ideas, please let me know and if I do figure it out, I'll post the solution on this thread.

 

Thanks again!

[ReadTheNetwork]

An old thread I know . Did you get anywhere with App-V and Small Basic?

[J_Worth]

No, I didn't. Have tried it with App-V 5.1 latest hotfix and still has the same issue. I have also tried the latest version of Small Basic to no avail. It's very annoying as its such a small application and would be ideal to be App-V'd.

[ReadTheNetwork]

I agree, I'm struggling to get Adobe CS6 to work fluently as App-V as well. I was hoping this would be a quick easy one to get be back on track :/.

Be nice to get everything V-Apped up.

[J_Worth]

I'm going to have another go during the summer holiday sometime to see if I can get it working.

[ReadTheNetwork]

I have hobnobs if you get it working . I've heard about PVAD and tried enabling that, but to no avail. Maybe you may have a better understanding or know if I'm going down the wrong route as I'm not entirely sure what PVAD is for.

Apps Needing PVAD | Confessions of a Guru

Permissions in the PVAD and VFS with App-V 5.0 | Virtual Vibes