J_Worth Posted September 2, 2015 Posted September 2, 2015 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 Posted September 2, 2015 Posted September 2, 2015 (edited) 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 Posted September 3, 2015 Posted September 3, 2015 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 Posted September 3, 2015 Author Posted September 3, 2015 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 Posted September 3, 2015 Author Posted September 3, 2015 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 Posted August 4, 2016 Posted August 4, 2016 An old thread I know . Did you get anywhere with App-V and Small Basic?
J_Worth Posted August 4, 2016 Author Posted August 4, 2016 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 Posted August 4, 2016 Posted August 4, 2016 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 Posted August 4, 2016 Author Posted August 4, 2016 I'm going to have another go during the summer holiday sometime to see if I can get it working.
ReadTheNetwork Posted August 5, 2016 Posted August 5, 2016 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
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now