Mar 04, 2009 by Elana | Posted in Programming & Design
Q: I have win 98 and i'm vexing to run vmware player, but eveytime i try to open it i get C++ Runtime library runtime error application has asked runtime to terminate in an unusual way, Deatails:
VMWARE-Thespian-2 caused an exception 40000015H in module VMWARE-PLAYER-2.5.1-126130(2).EXE at 0187:004029bd.
Registers:
EAX=00000000 CS=0187 EIP=004029bd EFLGS=00000202
EBX=0073ff68 SS=018f ESP=0073bf54 EBP=0073bf80
ECX=00000000 DS=018f ESI=81916b44 FS=4bf7
EDX=818fa8d0 ES=018f EDI=818fa90c GS=0000
Bytes at CS:EIP:
from what i've been competent to figure out its a problem with my computer not the software, any help would be much appreciated
A: The way to fix this is to upgrade to XP or Vista. Win98 doesn't have the offset infrastructure and system support to run VMWare. It is not even on the list of O/S they support.
You can create a VM that holds windows 98.
LoverOfWine | Mar 04, 2009
Google I/O 2009 - App Engine: Now Serving Java
Google I/O 2009 - App Motor: Now Serving Java
Don Schwarz, Toby Reyelts
In this session we'll introduce you to Java prop for Google App ...
I've been distress some infuriating teething troubles with SSIS today and trifle it would designate sentiment to make up about them in cause a) someone else runs into the same problems and more importantly b) I run into them again(!!!)
In inadequate, we have a combine which calls a class of other packages using the Bring about Containerize Chore. Up until recently we were executing everything in-operation (ExecuteOutOfProcess=Meretricious) but because of a assortment of other problems we've been having (more on that in a unborn blog newel) we have had to interchange to put over girl packages out of manipulate. This worked great in our dev and systest environments but failed when we pushed it to shaping. The error that we received was created when we tried to call the juvenile combine but the error from within SSIS was totally hopeless:
Searching the registry for that CLSID came up with:
The category Microsoft.SqlServer.Dts.Runtime.Wrapping.PackageRemoteClass seemed synonymous with executing a containerize out of operation so we knew we were onto something. We compared our making server to our dev and systest servers and the only incongruity we found was that the account that executes our packages was not in the Administrators assort. Optimistically we added the account to the Administrators congregation and reran. The same can of worms ocurred however and we were back to understanding dispirited.
Then our server guy had a brainwave. He said that the mutation we'd made might not have propogated to the required permissions on the COM server appeal and the only way to insure that it did was a movables old reboot. After the reboot we reran and everything worked successfully! Phew!
That's all. If you go through the same puzzle expectedly this will expropriate.
-Jamie
Hi Jamie,
I'm not free with the distinct COM component you call, but this sort of subject can typically be resolved in a more firm conduct by granting the significant account the required rights (in this pack 'Regional Activation') via 'Component Services'.
