Post subject: Unpacking of SCO boot media Posted: Fri Sep 07, 2018 7:15 pm
Joined Fri Jan 15, 2010 10:53 am
Posts 50
Hello. Please help me with unpacking of SCO boot disks available here (and particulary 'uod429a.Z' for Open Desktop 3.0): http://www.lubkin.com/SCO/boot-media.html When I tried to unpack on Unixware 7, it gives an error "Not in compressed format".
Post subject: Re: Unpacking of SCO boot media Posted: Sat Sep 08, 2018 3:37 am
Joined Sun May 13, 2007 12:42 am
Posts 2406
Code:
$ curl -O ftp://ftp.sco.com/pub/SLS/xnx264.n1.Z % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 277k 100 277k 0 0 535k 0 --:--:-- --:--:-- --:--:-- 534k $ uncompress xnx264.n1.Z $ ls -l xnx264.n1 -rw-r--r-- 1 root staff 737280 Sep 7 19:35 xnx264.n1 $ man compress | head
COMPRESS(1) BSD General Commands Manual COMPRESS(1)
NAME compress, uncompress -- compress and expand data
Post subject: Re: Unpacking of SCO boot media Posted: Sat Sep 08, 2018 8:41 am
Joined Fri Jan 15, 2010 10:53 am
Posts 50
Kenneth wrote:
Code:
$ curl -O ftp://ftp.sco.com/pub/SLS/xnx264.n1.Z % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 277k 100 277k 0 0 535k 0 --:--:-- --:--:-- --:--:-- 534k $ uncompress xnx264.n1.Z $ ls -l xnx264.n1 -rw-r--r-- 1 root staff 737280 Sep 7 19:35 xnx264.n1 $ man compress | head
COMPRESS(1) BSD General Commands Manual COMPRESS(1)
NAME compress, uncompress -- compress and expand data
Post subject: Re: Unpacking of SCO boot media Posted: Tue Sep 11, 2018 3:51 pm
Joined Fri Jan 15, 2010 10:53 am
Posts 50
Thank you everybody. Now I've successfully unpacked uod429a.Z on Fedora and now can test SCO Open Desktop 3.0 (CD-ROM without boot floppy is available on FTP). It looks like gzip works differently on Linux and BSD.
Post subject: Re: Unpacking of SCO boot media Posted: Sat Sep 15, 2018 2:45 am
Joined Fri Sep 14, 2018 11:36 pm
Posts 4
It could be interesting to see if there is something different about the archive format that is making it behave that way. If you ran the "file" command on the archive on a modern Linux system, does it report back something unexpected?
Users browsing this forum: No registered users and 2 guests
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum
All views expressed in these forums are those of the author and do not necessarily represent the views of the BetaArchive site owner.