I'm trying to install Microsoft Expressions Encoder 4 SP 1 on a fully-updated 32-bit Windows XP Pro SP3 guest running on a Debian wheezy host (AMD 64 kernel).
The installer gets past the "unpacking" phase and adds a button to the Windows Task Bar, but never actually manages to display the setup window for the program. Task Manager reveals that Xsetup.exe is taking up over 90% of CPU ... forever. So far I've let it run for an hour twice.
I've tried running the installer as Administrator. No dice. I tried reverting to VGA mode because of reports on MS's site of video issues preventing installation. No dice. I tried to install in Safe Mode and was told that an index has to be greater than zero!
I've downloaded the installation package twice to be sure it had not become corrupted. No dice.
I would appreciate any advice on how to debug this or move forward.
Also entered as ticket 9070.
Expressions Encoder install stalls after uncompressing files
-
BillG
- Volunteer
- Posts: 5106
- Joined: 19. Sep 2009, 04:44
- Primary OS: MS Windows 10
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows 10,7 and earlier
- Location: Sydney, Australia
Re: Expressions Encoder install stalls after uncompressing files
HAving read the system requirements for this program I would not expect it to run in a virtual machine.
•Support for Microsoft DirectX® 9.0 graphics with Windows Vista Display Driver Model (WDDM) Driver, 128 MB of graphics RAM or more, Pixel Shader 3.0 in hardware, 32-bits per pixel
•Support for Microsoft DirectX® 9.0 graphics with Windows Vista Display Driver Model (WDDM) Driver, 128 MB of graphics RAM or more, Pixel Shader 3.0 in hardware, 32-bits per pixel
Bill
-
carlf
- Posts: 7
- Joined: 29. Jan 2010, 04:39
- Primary OS: Ubuntu other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows XP, CentOS
Re: Expressions Encoder install stalls after uncompressing files
BillG:
ut
Thanks for the response. Couldn't the stupid installer just say that my system doesn't meet the requirements, though? I hate silent failures.
I just want to use it to transcode, dammit. I don't need hardware support, since I don't care if it takes a long time.
No way to have VB lie about hardware support, eh?
Again, thanks.
ut
Thanks for the response. Couldn't the stupid installer just say that my system doesn't meet the requirements, though? I hate silent failures.
I just want to use it to transcode, dammit. I don't need hardware support, since I don't care if it takes a long time.
No way to have VB lie about hardware support, eh?
Again, thanks.