• Autodata 3.24 won't run on Win7
    3 replies, posted
Hello gang. I've been tasked to install Autodata 3.24 on my dad's laptop. He used to have it on an older laptop that ran WinXP and it installed without a problem. The software is fairly old as far as I gather and the only install options I get are for Vista and older(As old as Win98). UAC has been disabled on the laptop since we got it so running as administrator isn't the problem.(I even tried clicking run as administrator just to rule it out but yeah. Not the problem). I tried running the installer in compatability mode for XP, Vista and Win98 with no luck. As it turns out, some dlls chilikat something or other will only run(be registered?) on vista or older. I keep getting an error that says something like: "Exception EOleSysError in module. Class not registered". I even went as far as to reinstall VMWare and run a virtual WinXP but apparently, it cannot run on Win7 but it knows when its being run in a virtual environment : / What the hell. Please help me guys D: Dad is counting on me.
[url]http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/windows-7-does-not-support-autodata-324-but/ce46e5e7-0669-45fd-8920-6e1edf82a0e6[/url] ?
[QUOTE=bohb;33211877][url]http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/windows-7-does-not-support-autodata-324-but/ce46e5e7-0669-45fd-8920-6e1edf82a0e6[/url] ?[/QUOTE] I read that entire thread. No fix or solutions.
That "Class not registered" error is probably caused because the program is looking for a specific version of some DLL that has an entry point, which isn't present. It could be caused due to conflicts or because the DLLs included with the application aren't compatible with the current version of Windows. Trying to tango in DLL hell is a bad idea, and can cause very nasty problems. I would not try installing said program on the machine, without being in some VM. Also, it's impossible for an application to know it's virtualized, unless some driver or other program is telling it that it is, which is likely not the case. Instead of using garbage VMWare, try Virtualbox with a Windows XP install instead.
Sorry, you need to Log In to post a reply to this thread.