system
8
Thanks again for your replies.
On how many systems have you tested it?
Switching graphics cards new/other drivers are installed and often causes conflicts.
- Physical WinXP PRO SP2 with ATI Radeon HD 3450 graphics card (Catalyst 10.10)
- Physical WinXP Home SP3 with Matrox G550 graphics card (PowerDesk 5.96.004)
- Physical Windows 7 Enterprise with ATi Radeon HD 4670 graphics card (Catalyst 11.1)
- VMware Guests WinXP PRO SP2, WinXP Home SP3, Windows 7 Ultimate hosted on machine 1 above
No graphics cards switches. All drivers have been reinstalled after proper reinstallation and cleanup of old drivers in Safe Mode. All VMware guests in testbed are fresh installations snapshots.
Nothing ever happens randomly on a system. It may seem that way to a user, but it is not random. Things always happen when a certain (or multiple) requirement is there.
Sure. But in any multitasking system where systems clocks and human activities are clearly out of sync, determinism is not that evident… Let’s say it’s not reproducible easily by a simple well known sequence like the one you describe.
http://support.microsoft.com/kb/316401
Oh, maybe I haven’t be clear enough. Error 0x0000007b is not a BSOD (STOP) message. It appears in a popup windows when I try to launch the virtualized app. The exact message is: “The application failed to initialize properly (0x0000007b).”
Concerning the so called known error “BSOD 0x00000050”, it has been reported in the forum that beta 5.1.x (x=667, 677 …?) was working with portable apps but I haven’t been able to retrieve the post so far… Nevertheless, I can’t rely on a beta version.
Regards.
Edit:
Edit:
Have you tried things on a clean (and properly) installed system?
If so, what is/was the result?
The results are identical on clean Virtual XP guests and “populated” physical XP systems and on XP Home SP3/Pro SP2(See my first post).
The only parameters that make thinapped apps behave in a particular way are (Thinapp OS version=4.0.4 or 4.6, Avast Version=5.0.507 or 5.1.889, the ThinApp package itself).
With Avast Free 5.1.889:
- Some 4.0.4 ThinApped [s]apps fail with BSOD[/s], some fail to initialize with error 0x0000007b, some work
- All 4.6.0 ThinApped apps fail to initialize with error 0x0000007b (no BSOD)
- I encounter some system recoverable errors in Explorer (no portable apps this time...)
Hmmm, I reconducted the tests on virtual testbed… no BSOD with 5.1.889, only “failed to initialize”. Was it on a physical machine or a mistake in my tests? I cannot retest on physical systems for now.