UE 1.5 works great on w98se -- usually.
however, the setup exe for Object Fix Zip (http://www.objectfix...s/objectfixzip/) crashes 1.5 -- UE15 reports "testing inno setup installer" then "test [OK]" then "extracting files from: Inno Setup Installer" then (X)
I don't know autoit, but that's an odd arrangement of quotation marks in the command string. There's an even number ok, but I can't pair them up sensibly.
AutoIt Error (X) Line 0 (File "C:\Program Files\Universal Extractor\UniExtract.exe"):
runwait($cmd & $inno & '-x -m'" & $file & $file & '"'& $oiutput, $ outdir)
Error: Unable to execute the external program.
A device attached to the system is not functioning.
Actually, this is the exact line of code:
runwait($cmd & $inno & ' -x -m "' & $file & '"' & $output, $outdir)
And those quotes do indeed match up. The full thing translates to the following (making assumptions for the paths):
c:\windows\command.com /c innounp.exe -x -m "c:\path\to\file.exe" | tee.exe c:\uniextract.exe
The problem you're seeing is not from invalid syntax in that line of code, but rather from various path and environmental variable issues that I could never work out quite right under Windows 9x. You can search through the really long main Universal Extractor thread for some more details if you'd like.
Would love to see the w98 switches turned on during compiles of v1.6 if possible. 98se ain't dead yet.
Actually, it is
. Software vendors can't support a given OS perpetually, and I think when the OS vendor itself end-of-life's the OS it's time to move on. Think about it - a line has to be drawn somewhere
, otherwise the same argument could be made for why Windows 2.0 isn't supported.
With that said, though, I didn't intentionally remove support for Windows 9x in UniExtract. It just never really worked right to begin with. :-) The big difference with 1.6, however, is that the current versions of AutoIt has moved to native Unicode binaries. Windows 9x doesn't support this, and as such new AutoIt applications will not run under Windows 9x. They still offer an option to compile ASCII binaries instead for use with Windows 9x, but I'm just not interested in maintaining separate versions, particular when one of them is for an OS that's been end-of-life'd and will be receiving no new security patches and updates. Plus, as I already mentioned, support for Windows 9x was always buggy to begin with (which is why it was never officially supported).
I don't mean to come across as an a** here, and I apologize if I do. This topic has come up a lot, and while I'd love to be able to fully support Windows 9x, it's just not feasible for a number of reasons.
Edited by nitro322, 08 May 2010 - 02:48 AM.