#59 closed defect (invalid)
Odin error
Reported by: | sanfords | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | general enhancement |
Component: | odin | Version: | |
Severity: | highest | Keywords: | |
Cc: |
Description
I installed odin32bin-20110710-release.wpi in eComStation 2.0 and tried to install Quicken 2001.
When I run "PE Install," I get error message: "Failed to start Win16 session."
When I run "Install," I get the error message: "Setup requires a different version of Windows."
Change History (2)
comment:1 by , 13 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:2 by , 13 years ago
Look at the old yahoo Odin group. There is a possible workaround in the files section: http://tech.groups.yahoo.com/group/odinusers/files/setup/ From the setup.txt file: Use of the setup.exe and _isdel.exe files.
Note: these are only good for use with installshield installers.
Case #1. A program is zipped and when it is unzipped you have to launch setup.exe. Upon launching setup winos2 launches but fails due to wrong windoze version. (If it installs then that is probably ok). Case #2. This one is the more common that I see of newer programs. A program is installed by launching an exe that could be named about anything (e.g. something.exe). After some harddrive activity an error come up setup.exe is not a 32bit exec. What has happened is that when something.exe is launched it expands into the temp directory (as defined in the config.sys) usually into a directory with a funny name . The easiest way for me to figure out what I am looking for in the temp directory is to delete everything in it then relaunch the something.exe. Whatever is in temp after that was put there by something.exe (it is possible that the directory gets deleted after acknowledging the error so check before acknowledging the 16bit error). In either case replace the setup.exe and _isdel.exe with the 32bit versions and run the setup.exe (in case #2 you have to do it from the temp directory not from something.exe). Hope this is not too convoluted and will be helpful.
The _setup.dll is a 32bit version included for completeness though the 16bit version works.
it seems quicken uses a old installation scheme. try to install it on win and transfer all files. there is nothing we can do about such cases.