@Xeraxic, how did you remove the timebomb in 7955.There is no expiration date shown in the "about windows" dialog of your screenshot.
Doesn't work for me & several others that posted in the Win8 forum here at MDL. Would you please post a screen shot of your admin command prompt showing the code you typed in & the response that it worked? I've been copy/paste the code in is that a possible reason it doesn’t work? TIA
.. I really dunno if it's working and I can't even test... but one thing it's surely CLEAR : If you only did "copy/paste" (like YOU said) ... HOW THE HELL you could pretend it would work ?!? Maybe if you correct {Drive} with your real Installation Drive Letter and {application exe} with the EXE filename that you want to launch , I could bet that you'll have a minimal chance to see if it's working or not... (just like the example that he made for Moorea...) ...don't you think ?!?
Thats what I've tried, still no joy. I didn't try typing my modified code in yet as I said above though. My Moorea worked out-of-the-box in Windows 8, as the Repack O'15 I used included a shortcut & was already modified.
Here is what I tried in the Win8 7955 Admin command prompt: C:\>"{Drive}:\Program Files\Common Files\microsoft shared\Virtualization Handler\CVH.EXE" "Virtual Command Shell 0015006C04090000" /c Q:\15006C.enu\Office15\{application exe} The filename, directory name, or volume label syntax is incorrect. C:\>"{C}:\Program Files\Common Files\microsoft shared\Virtualization Handler\CVH.EXE" "Virtual Command Shell 0015006C04090000" /c Q:\15006C.enu\Office15\{WINWORD.EXE} The filename, directory name, or volume label syntax is incorrect. C:\>{C}:\Program Files\Common Files\microsoft shared\Virtualization Handler\CVH.EXE The filename, directory name, or volume label syntax is incorrect. C:\>Program Files\Common Files\microsoft shared\Virtualization Handler\CVH.EXE 'Program' is not recognized as an internal or external command, operable program or batch file. *Has anyone actually got this to work? Any suggestions are appreciated.
You've probably forgot quotes " so try that: "C:\Program Files\Common Files\microsoft shared\Virtualization Handler\CVH.EXE" "Virtual Command Shell 0015006C04090000" /c Q:\15006C.enu\Office15\montage.exe" ---> for Morea...etc...
It works but not for long. Word launched but then closes a few seconds later, it happens with other apps too. Only moorea works fine.
Thank you helper7, that advise worked for me getting Lime to work. Attached thumbnails: Q Drive applications Admin Control Panel code used About Lime (Limestone) Lime - first window
Very strange...Try to set Win95 compatibility mode for Word or PW then try to open it from CMD....It will show you error but as soon you click OK it closes :S and here another trick....Open Excel and when it open then press left click on the mouse and drag around a little bit...You will see that Excel will not automaticly quit but as soon you will release it it will shut down xD
The programs were crashing a few seconds after i loaded them up for a bit, but then they stopped crashing and started working. Today they started crashing again, very weird. Noo.. I changed the date when i installed it, it will expire, but it doesn't show the date.
Check this: Code: LevelDate and TimeSource Event IDTask Category Warning1/06/2011 13:25:49Application Virtualization Client3020(11) Information1/06/2011 13:25:51Office Software Protection Platform Service1003None Information1/06/2011 13:25:51Office Software Protection Platform Service1003None Information1/06/2011 13:25:51Office Software Protection Platform Service1003None Information1/06/2011 13:25:52Office Software Protection Platform Service1003None Information1/06/2011 13:25:52Office Software Protection Platform Service1003None Information1/06/2011 13:25:52Office Software Protection Platform Service1003None Information1/06/2011 13:25:53Office Software Protection Platform Service1003None Information1/06/2011 13:25:53Office Software Protection Platform Service1003None That's what happens when running winword.exe with the command on the first page. The warning is something about a wrong url for downloading packages, but this isn't necessary cause al files are in the Q: drive anyway. The other ones are all things from OSPP. Now when I launch my non-genuine Office 2010 there are 4 OSPP actions logged with simular propperties, 4 is less than the 8 events here, but still. I've also noticed that the delay between launching an app and the crash is about the same as the delay between launching a non-genuine Office 2010 app and the appearance of the red bar. So I think OSPP simply detects Office is non-genuine, and then fails to take some action (like applying the red bar). The stupid thing is that I can't activate MSO 2010, it says Windows is non-genuine. Windows is activated, but I changed files to unlock features etc. Probably that's why Office 2010 detects windows as non-genuine and fails to activate. Office 15 probably autoactivates or something like that, but also fails at this because of non-genuine windows. It looks to me that first Windows needs to be made fully genuine, and afterwards Office won't be a problem anymore. Probably Office will work just fine on an untouched Windows 8 install, withoud mods to unlock features.
I'll install 7959 on Virtualbox in the evening and post the results. If Office 15 works well, we'll know the solution.
Actually, why can't you activate Office 2010? I use Office 2010 on both 7959 and 7955 and it works well. Both have BluePill installed, respectively 2.0 and 1.6 and Office 2k10 activates just fine.
That can be caused by the fact that I'm using some of the old scooby files. Except for computer propperties and MSE everything works fine, so I never installed bluepill.