4.005 won't run on Vista Business - Microstudio 4.006 fixes problem

[norrodb]

Hi !

I searched the forum, but did not find this issue.

I just purchased and installed 4.005 on my laptop running

Vista Business
2GHz Duo
2GB ram
ATI Mobility Radeon x2300 with 64 dedicated RAM, 800+MBram available
DIrectX10

Microstudio installed with out issues, but when I launch it, it never comes up on my desktop. I can see the process running at about 45% cpu, but never shows.

EDIT: to add, the task does not show in applications list, but only in processes.

I have .Net Framework 2.0 and ran windows updates.

I am now at a road block on what to try next.

Any ideas?

Thanks !
Brent

[ddouglass]

When you ran the Windows Update, did you use the Auto Update or the Express Update from their website?
If so you need to run the Custom Update to get other updates that Microsoft does not consider as critical.
The other thing I can think of right now is to look at the Microstudio folder with Windows Explorer. At the top of the window you will see a button labeled Compatability Files. You need to turn this on.
Last I would say try uninstalling it, restart the computer, then re-install and restart it again. It may just be that a component of it didn't install correctly.

[norrodb]

Thanks Dale.

Might be worse then I thought. I do not see a "Compatibility Files" button ??? Is there an option to make that button available?


I did a custom all available updates.

[ddouglass]

Don't know about that. It should be there if it hasn't been set before and the default for Vista is to not have it set. Did you try reloading the program?

[dcrog]

Did the demo program work?

[norrodb]

I stripped out the program, and installed again. No Change.

I stripped out the program, and installed the demo. Same ting.

I launch it, and get the hourglass for a couple of seconds. The application initializes in the task mamanger, but not in the applications list. The app is not froze as I can watch CPU and memory usages chnages constantly. Over time, the memory usage will keep climbing.

I also removed all .net Framework and patches , and reinstalled.

Really at a loss here.

I should have tried the demo before paying for the product

[admin]

norrobd, we are hoping you can run our 4.006 Beta 1 version I sent you the link to, with a special debug logging feature, and then post your results and the .log file in this Thread.

We want to work on this problem first thing Monday (tomorrow) morning. If we don't get your log file, we'll have to displace this until later in the week to keep moving forward.

[norrodb]

Originally Posted by admin

norrobd, we are hoping you can run our 4.006 Beta 1 version I sent you the link to, with a special debug logging feature, and then post your results and the .log file in this Thread.

We want to work on this problem first thing Monday (tomorrow) morning. If we don't get your log file, we'll have to displace this until later in the week to keep moving forward.

Thanks for the link. Looks like I won't be of much help.

I installed the Beta, and the application runs fine !

So then I uninstalled, rebooted, and reinstalled 4005. It now runs fine too :() I have not done anything with my laptop since we first started. I was in Atlanta, and flew back to Pittsburgh, so my laptop has been sitting all weekend.

This is the order of things.

Installed 4005 - not working
Fully Updated Windows 4005 not working.
Removed .Net Framework and reinstalled. No change
Removed 4005
Installed Demo version. - Same reults.
Uninstalled demo
Installed Beta - It ran fine.
For grins, uninstalled Beta, reinstalled 4005 and it works fine !

Not sure what to tell you now except doesn't look like VISTA BIZ edition is an issue? Of course my UAC is still disabled.

I really appreciate your efforts.

[admin]

I forgot to mention this change we made in 4.006 Beta 1:

FIXED Windows Vista Compatibility - Vista does not allow editing or changing any files saved in the \Program File\ path. Version 4.006 detects Windows VISTA on installation. If updating a prior Microstudio version (including 4.005), existing working files are automatically moved from the C:\Program Files\... folder to a new C:\Documents and Settings\[User]\Local Settings\Application Data\MTU\Microstudio\ folder. For new installations the working files are created in this new folder.

This would explain why 4.006 worked, and 4.005 also worked after installing 4.006. The working files that we use and EDIT, that Vista doesn't like being in C:\Program Files\ path are now moved. That would totally explain what you saw.

Thus, this has been an excellent test and verification that our changes are working.

We are moving on with 4.006 Beta 2, which has a major overhaul of our Import Tracks code to automatically retry when any error remains after the first read from the disc track.

Watch for its release. It'll be a free upgrade for you from 4.005.

Thanks again for your feedback.

[norrodb]

Awesome support guys

Originally Posted by admin

I forgot to mention this change we made in 4.006 Beta 1:

FIXED Windows Vista Compatibility - Vista does not allow editing or changing any files saved in the \Program File\ path. Version 4.006 detects Windows VISTA on installation. If updating a prior Microstudio version (including 4.005), existing working files are automatically moved from the C:\Program Files\... folder to a new C:\Documents and Settings\[User]\Local Settings\Application Data\MTU\Microstudio\ folder. For new installations the working files are created in this new folder.

This would explain why 4.006 worked, and 4.005 also worked after installing 4.006. The working files that we use and EDIT, that Vista doesn't like being in C:\Program Files\ path are now moved. That would totally explain what you saw.

Thus, this has been an excellent test and verification that our changes are working.

We are moving on with 4.006 Beta 2, which has a major overhaul of our Import Tracks code to automatically retry when any error remains after the first read from the disc track.

Watch for its release. It'll be a free upgrade for you from 4.005.

Thanks again for your feedback.

[admin]

We try!

Thanks for noticing. Whenever we find a problem with any product that is a real "nasty", we do everything we can to remove it quickly.