Re (6): [Oberon] Homework on ZipTool & MS dud-partitions

cglur at onwe.co.za cglur at onwe.co.za
Sun Sep 8 19:10:10 CEST 2002


Peter E. wrote:
> If someone wants to extract a specific file
> or files with unconventional names, 
> replacement names are specified.

Does 'unconventional' mean invalid for n-o ?

> These can 
> be extracted later using :
> "ZipTool.Extract 
> badfilename1 => goodfileanme1
> badfilename2 => goodfilename2 ~"

I get errors:
ZipTool.Extract C:Temp.zip DUG_IDE.C => NewName1 ~
  == file encrypted /compression method not supported

ZipTool.Extract C:Temp.zip "DUG_IDE.C"  => NewName1 ~
   ==  NewName1 file encrypted / compression method not supported, 
        could not extract

Can this version { ZipTool1.Arc (Aug  5) }  handle DOS fileNames ?
Ie. invalid n-o file names, like other commands can.
eg.   OFSFATTools.ChangeDir "D:D-386-4.OBN/"

Native oberon surely must give us access to the WORLD.
ZipTool.Mod is seriously lacking if we can't process the many
*.zip files 'out there'.

I (or some one else) could look at some code of the many procedures
that 'handle' non-native-oberon file names, apparently (by convention)
by enclosing in "quote-marks", if it is confirmed that my errors:
     'file encrypted /compression method not supported'
is in fact cause by the 'DUG_IDE.C' invalid filename.
The ZipFiles extracted OK with linux and DOS /  PKunzip .
Also ZipTool1.Arc (Aug  5) extracts OK for n-o valid fileNames.

-- Chris Glur.

PS. I don't know how these non-ascii chars will email, but the Temp.zip 
starts like this (normal PKziped file):
PK    ¶,[3Úe  V  	   DUG_IDE.C
 ----------------

BTW. to test MS / PKunzip I again confirmed the 'power' of n-o:
MS-DOS can't read my C: , but n-o can !! 
So I need to use n-o to copy C:/FLOPPY.BAK/Temp.zip to D:
in order to test DOS-Pkunzip.  
I have considered that a 'newer BIOS' could perhaps handle my FAT
IDE0#01, but an aquaintance who has the latest, also fail to see this IDE.

 This relates to my previous post re. distributing a standalone
1M4 diskettes to show Microsoft users what native oberon can do for
them when their IDE is corrupted -  what MS tools apparently can't do !





More information about the Oberon mailing list