Help - Search - Members - Calendar
Full Version: UE_1.5 works on w98se
MSFN Forums > Member Contributed Projects > Other Member Contributed Projects > Universal Extractor

   


Google Internet Forums Unattended CD/DVD Guide
Molecule
UE 1.5 works great on w98se -- usually.

however, the setup exe for Object Fix Zip (http://www.objectfix.com/products/objectfixzip/) crashes 1.5 -- UE15 reports "testing inno setup installer" then "test [OK]" then "extracting files from: Inno Setup Installer" then (X)
QUOTE
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.

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.

Would love to see the w98 switches turned on during compiles of v1.6 if possible. 98se ain't dead yet.
nitro322
QUOTE (Molecule @ Nov 9 2008, 08:57 PM) *
UE 1.5 works great on w98se -- usually.
however, the setup exe for Object Fix Zip (http://www.objectfix.com/products/objectfixzip/) crashes 1.5 -- UE15 reports "testing inno setup installer" then "test [OK]" then "extracting files from: Inno Setup Installer" then (X)
QUOTE
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.

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.

Actually, this is the exact line of code:

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):

CODE
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.

QUOTE (Molecule @ Nov 9 2008, 08:57 PM) *
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 Windows 9x. 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.
Philco
QUOTE (nitro322 @ Nov 10 2008, 12:54 AM) *
QUOTE (Molecule @ Nov 9 2008, 08:57 PM) *
UE 1.5 works great on w98se -- usually.
however, the setup exe for Object Fix Zip (http://www.objectfix.com/products/objectfixzip/) crashes 1.5 -- UE15 reports "testing inno setup installer" then "test [OK]" then "extracting files from: Inno Setup Installer" then (X)
QUOTE
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.

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.

Actually, this is the exact line of code:

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):

CODE
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.

QUOTE (Molecule @ Nov 9 2008, 08:57 PM) *
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 Windows 9x. 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.


Only note: Any version (old) with support win98? Test 1.5 - error unpacking.....
jds
QUOTE (nitro322 @ Nov 10 2008, 03:54 PM) *
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.


Is there any way to hack a 1.5 & 1.6 hybrid together that can work with W98?
Alternatively, using UE with KernelEx?

I tried to use KernelEx to install 1.6, which seemed to work (install), but all it does is produce an empty file called "&1" and give an error like "I should be able to extract this, but something went wrong, so you want to view the log file?". There isn't a log file anyway.

Interestingly BTW, the AutoIt v3 home page says "Compatible with Windows 95 / 98 / ME / NT4 / 2000 / XP / 2003 / Vista / 2008".

Joe.
xenon2050
I can't help but shake my head when people say they are using windows 98se. I can understand if you have it running on a old computer for computer games or things like that, but if you are using UE on it it makes me wonder if it isn't the primary computer... I mean comeon people, its been out of support for 3 years and is over 10 years old.... smile.gif I'd rather see the program develop on current OSes instead of spending time making it work on 98se, which is a waste of time IMHO.





Google Internet Forums Unattended CD/DVD Guide

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.