

 ea 18 nor
 ************
Topic 18        Sat Jun 22, 1991
C128.JBEE [* Sysop *]        (Forwarded) 
Sub: CS-DOS & REU C1750 & LHA & Autoexec    

 One of the most often asked questions is how to set up the C128/C1750/
 LHA/Autoexec file to make SFX archives.  The autoexec file follows...
106 message(s) total.
 ************
 ------------
Category 3,  Topic 18
Message 1         Wed Mar 03, 1993
M.MINNIG                     at 04:56 EST
 
 Thanks!
 The key was the drive-letter prefix.  None of the docs mentioned it, but the
 proper syntax must include it.  Also, it doesn't matter whether or not you
add
 the "arc" suffix to the filename.

 Next project - creating an .sfx file; any tips?
 :)

 Michael
 ------------
Category 3,  Topic 18
Message 2         Wed Mar 03, 1993
HOWIE-CBM                    at 19:05 EST
 
 Michael,

 Easy! :)

 LHA -s a:filename.sfx a:file4sfx b:file4sfx c:etc

 And, if you want the sfx to have a custom title screen:

 LHA -s a:title a:filename4sfx b:etc

 A file with the name TITLE would then have to be in drive A.  There
 is a custom title maker which I put into the library.  Just do a search
 on HOWIE-CBM and it will show up.

 Howie
 ------------
Category 3,  Topic 18
Message 3         Thu Mar 04, 1993
CBM-MARK                     at 00:46 EST
 
 I'll keep my $.02 outta here this time ;D

          Mark
 ------------
Category 3,  Topic 18
Message 4         Thu Mar 04, 1993
HOWIE-CBM                    at 01:58 EST
 
 Mark,

 Your $.02 is *always* welcome.

 Just don't say anything about sfx suffixes....   :)

 Howie
 ------------
Category 3,  Topic 18
Message 5         Fri Mar 05, 1993
CBM-MARK                     at 00:11 EST
 
 LOL!   It's a deal ;D
 ------------
Category 3,  Topic 18
Message 6         Fri Mar 05, 1993
HOWIE-CBM                    at 04:48 EST
 
 Hmm...

 Speaking of LHA....

 Has anyone taken a look at an LZH directory, and the date and
 time of file creation?

 The date seems to come out fine, but it always seems to be
 0:01 AM.  Doesn't seem to make a difference if it is an LZH
 or SFX.

 And, the worst part of it is that after I've run LHA, the
 cs/dos system time has been reset to 1:00 AM, which unless
 reset will get plowed into everything else.

 So.....

 What I see happening is that LHA itself is resetting the
 cs/dos system time, and then using the newly and incorrectly
 set new time.

 Now, this doesn't happen with ARC.

 What to do?

 Howie
 ------------
Category 3,  Topic 18
Message 7         Mon Mar 08, 1993
C128.JBEE                    at 15:10 EST
 
  
 lha -s, a:filename.sfx a:title a:whatever*

 As for date and time bugs, there are a lot of little buglets to be
 squashed ;)
 ------------
Category 3,  Topic 18
Message 8         Sun Apr 11, 1993
R.HIGDON3                    at 02:57 EDT
 
Hi!  Well, I think LHARC is a fine compression utility, but I have a couple of
questions about it.  The file SFX2LZH is supposed to convert a SFX archive to
a LZH archive, but I couldn't get it to work. When I use the LHD program, the
resulting LZH archive seems to be empty. Has anyone else had a problem using
SFX2LZH? Also, in the file LHAV12.ARC is the source code for SFX. One of these
files is SFX2LZH.EXE. Not having an IBM-compatible PC, would I be able to use
a file with the EXE extension?  One last quesion is since I don't have a 1750
REU, could I still convert a LZH archive to a SFX archive? Thanks...:)
 ------------
Category 3,  Topic 18
Message 9         Sun Apr 11, 1993
CBM-ED [e.g.bell]            at 08:50 EDT
 
 One thing I'd like to see CS-DOS do when it is upgraded is to allow use
 of the RamLink in addition to the REU for creation of SFX/LZH files.
 Howzabout that John?  ;^)
 ------------
Category 3,  Topic 18
Message 10        Sun Apr 11, 1993
CMD-DOUG                     at 12:13 EDT
 
I'd also like to see path support. We all know that archives coming from other
machines may have subdirectory paths in the filenames, which right now is
ignored by the dearchiving modules in CS-DOS. It would be a nice added bonus
if we too could make use of those paths. :)
 ------------
Category 3,  Topic 18
Message 11        Mon Apr 12, 1993
HOWIE-CBM                    at 12:30 EDT
 
SFX2LZH works fine for me!

All it does (as far as I know) is strip the SFX header leaving you with an
LZH.  Actully, if I remember right, it leaves your SFX intact, and writes a
new file with the LZH extension.  If you like, I will check on this.

Can you give more details on what you are doing to help ID the prob?

Any EXE is for running on ms/dos, so it would need "translation" before it
could get accepted as an autoexec under cs/dos.

Superb question about converting and LZH to SFX!!  In fact one which I have
been chattering about with some sysops here on line.

The easiest way, is to have an SFX header, and then simply append to it any
LZH file which you want to make into an SFX.

If you'd like, I can make up a "generic GEnie" header, including title screen,
that could be the base for an SFX, to which anyone can then append LXH's.

Howie
 ------------
Category 3,  Topic 18
Message 12        Mon Apr 12, 1993
R.HIGDON3                    at 21:10 EDT
 
Well, when I use SFX2LZH, it seems to work fine. It writes the LZH archive to
the disk (12 blocks shorter than the SFX), but when I try to display the files
within the LZH achive using either LHD or LHX, it doesn't work. I did check
the first sector of the resulting LZH archive using a disk editor, and it
seems to be the same as what the SFX would be. If I remember right, it's not
until the third sector of the resulting LZH that it begins to look identical
to one of my good LZH archives. That's about all I can tell you.
 ------------
Category 3,  Topic 18
Message 13        Tue Apr 13, 1993
HOWIE-CBM                    at 01:35 EDT
 
This is puzzling.....   :?

Only thing I can think of is that there is some variable when you run sfx2lzh
that isn't there when I do it.  But, what that mght be I do not have the
foggiest idea...

I really cannot think of anything else to suggest.  Maybe someone else?

Howie
 ------------
Category 3,  Topic 18
Message 14        Wed Apr 14, 1993
C128.JBEE                    at 06:05 EDT
 
 The PC sfx2lzh.exe is just a short PC utility to strip the SFX header
 away from the LHA archive.  Almost all the PC archivers do it automatically
 now on any self extracting LHA file (PC-Amiga-Atari-Mac) so the program
 itself is pretty much obsolete because it is no longer needed.  That was
 basically added by Chris as a utility to help the former Flagship staff
 that used PCs to download files.  Since all I use are 128s, I don't use the
 utility :)

 I am still trying to duplicate that empty archive problem.

 >ED,
 >One thing I'd like to see CS-DOS do when it is upgraded is to allow use
 >of the RamLink in addition to the REU for creation of SFX/LZH files.

  YES!

 >Doug,
 >I'd also like to see path support.

 Double Yes :D
 ------------
Category 3,  Topic 18
Message 15        Wed May 05, 1993
HOWIE-CBM                   at 02:44 EDT
 
 <<double slap upon the embarassed forehead>>

Of course......

The reason that LHA creates all of its SFX and LZH file contents at 1:00 AM is
because LHA is the only compression module which reports to the user the time
lapsed for the file creation.  Therefore, it is safe to presume that LHA is
resetting the cs/dos clock to 1:00am and figuring lapsed time from there.

Prob with this present setup is that all the files then get time stamped with
1:00 am, and when the SFX or LZH has been created, the time is not reset, but
left at whatever time has elapsed for file creation, plus 1:00 am, or in other
words, usually a few minutes after 1:00.

At least none of this affects LHA's use of our RL'S RTC's dates, whlich remain
intact, and properly recorded.  It is sorta nice to see a file  uploaded to
the Library, on lets say, 05/05/93, and then later observe the files
dissolving with a creation date of 05/05/93.  Maybe this is just my
preference, but I like it.

I wonder if a new LHA can have a work-around for the time prob, however?  It
is nice to have the time reported, but maybe this can get done with the time
remaining properly set, and not unnecessarilly resetting it?

Did I just get carried away or what?

Howie
 ------------
Category 3,  Topic 18
Message 16        Fri May 07, 1993
C128.JBEE                    at 01:01 EDT
 
 Proper time/date stamping with support for CMD devices is on the bill.
 ------------
Category 3,  Topic 18
Message  18       Sun May 23, 1993
D.VARGO                      (Forwarded) 
 
Could someone please e-mail me the names of the files required to create sfx
files for both the 64 and 128.  I want to upload some files to  genie, and I
know I appreciate the convinience of sfx files, so I'd like to be able to
create them for the other users on line here. Thanks much!
 ------------
Category 3,  Topic 18
Message 19        Sun May 23, 1993
C128.JBEE                    at 18:02 EDT
 
 Hi :)

 Files needed for CS-DOS 128 to make SFX files.

  7800 CS-DOC15.SFX             X C.SMEETS     900218   44100    440   2
       Desc: CS-DOS/ARC128 - Part 2 of 2
  7799 CS-DOS15.SFX             X C.SMEETS     900218   50400    484   2
       Desc: CS-DOS 1.5/ARC128 - Part 1 of 2
  8223 LHAV12.ARC               X C.SMEETS     900902  152460    278   2
       Desc: Update to LHARC128 for CS-DOS
 ------------
Category 3,  Topic 18
Message 20        Tue Jun 29, 1993
S.CRAIK [Steve]              at 02:26 EDT
 
 Howie,

 re: work-around for time prob  LHA  etc.

  Wazabout a BATCH file

 Here is the beginings of what I've done:

 batchfile name:  lhat  ; means call on "lha" and another batchfile
                        ; of updating the time from a CMD device w/RTC

if "%1" = " " goto usage if "%2" = "-s" goto selfx if "%3"= " " goto usage
echo "Starting to LHArchive %1" goto create :selfx echo "SFX function not
implimented this Version" goto donelist echo "Starting the Create %1.sfx"
:create lha %1 %2 %3 %4 %5 %6 %7 %8 %9 goto fin :usage echo "Usage: Create
LZH's or SFX's and adjust CSDOS from CMD with RTC's" goto done echo "Syntax: 
lhat lharchive.name <-s> pattern" :fin echo "Correcting the Time" rltime :done
;

 "rltime" is just a basic thing to fetch the time from the CMD device
 it can be a portion of the program you did where it clears the screen
 and types in the time based on the info from the CmD device.

  Oops I forgot  to include the word TIME in the  echo "Usage:" line
 and I think that I would like to change the Syntax order conforming more
 to "lha"  as far as the entering/calling on "LHAT" to perform.

Steve Craik
 ------------
Category 3,  Topic 18
Message 21        Tue Jun 29, 1993
HOWIE-CBM                    at 07:29 EDT
 
 Steve,

 A great idea and one a lot of us will use once it is complete  Thanks!!

 Here it is again, posted with an *SN to keep formatting, and with your
 addition:

 ;batchfile name:  lhat 
 ; means call on "lha" and another batchfile
 ;                      
 ; for updating the time from a CMD device w/RTC
 ;  
 if "%1" = " " goto usage
 if "%2" = "-s" goto selfx
 if "%3"= " " goto usage
 echo "Starting to LHArchive %1"
 goto create
 :selfx
 echo "SFX function not implimented this Version"
 goto donelist
 echo "Starting the Create %1.sfx"
 :create
 lha %1 %2 %3 %4 %5 %6 %7 %8 %9
 goto fin
 :usage
 echo "Usage: Create LZH's or SFX's and adjust CSDOS' time from a RTC"
 goto done
 echo "Syntax:  lhat lharchive.name <-s> pattern"
 :fin
 echo "Correcting the Time"
 rltime
 :done
 ;

 A good start!  :)

 Howie
 ------------
Category 3,  Topic 18
Message 22        Sat Aug 14, 1993
HOWIE-CBM                    at 06:30 EDT
 
 Rose,

 To answer your ? about cs/dos, a good starting point for seeing if
 you can get things running again would be to take a look at any of
 your autoexec and related files.  Specifically what you are looking
 for are drive designators.  Before *every* command that gets
 called from a drive be sure to have a drive designator, that
 agrees with your system setup.

 As an example of what I am referring to, here is an autoexec.
 Notice how every command is preceeded by its drive letter:

 slow
 bank15:y=peek(57094):poke 57094,y+1:poke 7136,abs(peek(57094)-y)
 z:if not errorlevel 1 z:autoexec2
 z:setram 21,3
 poke 7120,2*16+5
 poke 7119,2*16+5
 poke 7136,1
 if errorlevel 1 goto ramdisk-already-there
 z:getram z:ramdisk
 :ramdisk-already-there
 if (peek(215) and 128) then fast
 poke 7150,4:poke 7151,96
 assign b 9,0
 assign c 10,0
 assign d 11,0
 assign e 12,0
 assign i 16,0
 assign j 16,6
 assign k 16,9
 run"settimeday",u16

 If this doesn't fix things hollar at me.

 Howie
 ------------
Category 3,  Topic 18
Message 24        Thu Aug 26, 1993
R.STOLL6                     at 01:43 EDT
 
Can anyone help me with arc128? I d/l.ed cs-dos15.sfx and the doc file, and
lhav12.arc.  But I could not get arc128 to dissolve the lhav12 file. In fact,
I can't get it to do much of anything. If I load and run it, I get a short
list of cmds, when running cs-dos. If I'm not running cs-dos, when I run
arc128, it breaks into the monitor. Now I have used arc230 before, and finally
used it to dissolve the lhav12 file. So any ideas as to what is wrong?

Next, I have two .lzh files from lhav12. I can get a list of what is in the
a21.lzh file, but when I try the sfx_src.lzh, it says can't open file. What is
going on here?  One more thing, I d/l.ed them with Wizard 128, ymodem, if that
makes any diff.  Still havn't figured the cs-dos out, but I'm working on it. I
think I'm going to love it, though.
 ------------
Category 3,  Topic 18
Message 25        Thu Aug 26, 1993
R.KNOP1 [Rob Knop]           at 22:01 EDT
 
Well, you don't say how you tried to use arc128 and the error you got, but I'd
give $10 that it's the problem that nearly everyone has with arc128 (and the
problem that stalled me on it for nearly a month way back when):

The problem is the help screen.  When you run arc128 without any options, it
prints a list of help commands, which (for instance) suggest that the usage
necesary to extract a file would be:

  arc/x filename.arc

However, this would work if the executable were named arc.  In reality, it is
arc128, so try instead the command line:

  arc128/x filename.arc

I predict this will clear up all of your problems.

Curious, are you running arc128 from the RAMDisk, having "install"'ed it?

-Rob
 ------------
Category 3,  Topic 18
Message 26        Sat Aug 28, 1993
H.HERMAN1                    at 04:57 EDT
 
Supplementing Rob's explanation, LHX, or LHD should be used when manipulating
an arc with an .lzh extension.

Howie
 ------------
Category 3,  Topic 18
Message 27        Sun Aug 29, 1993
R.STOLL6                     at 02:27 EDT
 
Well I do feel kind of dum now.  I d/l'ed the assist files, and arc128/x was
in them, and it worked just fine. So, I renamed arc.  And yes I'm using the
ramdisk. Would be interested to know what the files in there do, that are not
listed in '.txt' files. And there are several, like link?  Anyway, when I
dissolve the lhav12 file, I get a checksum error on sfx_src.lzh file.  So does
this mean I got a bad d/l?  One more thing, if I put the ramdisk in the 128,
bank 1, and use a 1700, can I still have lha use the 1700 ram pack?  I have
set the ramdisk in the 128 bank 1, and then can't reset it into the ram pack. 
I guess what I need to do is find out how to make the 1700 into a 1750.  And
thanks for the help.
 ------------
Category 3,  Topic 18
Message 28        Mon Aug 30, 1993
R.KNOP1 [Rob Knop]           at 01:07 EDT
 
Re: arc vs. arc128, no need to feel stupid!  It's an obvious flaw in the auto-
help of arc128, and this is one question that nearly everybody using CSDOS for
the first time has.

Re: using the 1700 for LHA even with the RAMDisk in Bank 1 on the 128, yes, I
think it should be possible.  Look at lha.txt, where it describes the poke
necessary to use LHA, and try specifying banks 0-1 of the REU.  Specifically,
before using lha, try

                    poke dec("1bcf"), 0*16+2

Re: upgrading the REU to 512K, if you are handy with a soldering iron, this
would probably be worth it; even if not, if you can get somebody else to do
it, it is probably worth it.  What sotware do you use?  There is a lot of
software out there that is more effective with a 512K REU than with a 128K
REU.  One such is CSDOS, so you can have the ramdisk in the REU (thus giving
you more ramdisk space and saving the RAM1 memory), as well as space for lha.
Also, if you use GEOS at all, a >=512K RAM unit of some sort is a virtual
necessity.

-Rob
 ------------
Category 3,  Topic 18
Message 30        Sat Sep 04, 1993
C128.JBEE                    at 17:33 EDT
 
 When dissolving some .ARC files you will get a version error at the end
 because of xmodem padding.
 ------------
Category 3,  Topic 18
Message 33        Mon Sep 06, 1993
M.COLWELL1 [MattMan]         at 14:46 EDT
 
Is there a easy way to chop x-modem padding?  I usually end up doing it
manually with a sector editor.

 ------------
Category 3,  Topic 18
Message 34        Mon Sep 06, 1993
R.KNOP1 [Rob Knop]           at 16:05 EDT
 
Sector editor is probably the safest way to do it, since you look at each file
individually and know exactly what you did, but it is a pain in the butt.

A lot of term programs will chop xmodem padding during download.  What term
program are you using?  The problem is, almost none of them will chop the
screwy version of Xmodem-1K padding that GEnie uses.  (RTCM128 might chop that-
 does it Ed?)

I have seen at least one program in the library that claims to remove xmodem
padding.  Do a search on the libraries for the keyword "xmodem".

-Rob
 ------------
Category 3,  Topic 18
Message 35        Mon Sep 06, 1993
C128.JBEE                    at 18:24 EDT
 
 ARC contains commands to strip XMODEM padding from an archive if you want
 to add to that archive later.
 ------------
Category 3,  Topic 18
Message 36        Mon Sep 06, 1993
CBM-ED [e.g.bell]            at 22:31 EDT
 
 RTCM128 does strip the GEnie padding that chokes some files.  This is 
 something that will affect either Xmodem 1k or Ymodem, and takes things 
 one step further than I think other programmers do, but it was written
 more with GEnie in mind.  I have used it elsewhere too tho.

 I was also going to suggest ARC, but John beat me to it.  heheh  And as
 Rob said, a sector editor *may* be the best, tho for a program file it 
 might be faster, if you are using a 128, to go into the monitor, load the
 file, find the end, and then just BSAVE @ the file back at the correct
 addresses.  You would have to locate the load address.  The end address
 is easily found (at least the one at the end of the load) by checking 
 addresses $00ae and $00af using the 'm' command of the monitor.  You can
 work back from there.

 ------------
Category 3,  Topic 18
Message 37        Tue Sep 07, 1993
H.HERMAN1                    at 02:49 EDT
 
Mattman,

If the padded file is 120k or less, BobsTermPro's buffer is an easy way to
strip x-mo padding.

For larger files....

Hmm....   Would ZED handle this?  Or, maybe Velvetta?  (I think Velveeta
mostly does CR/LF things, however.)

Howie
 ------------
Category 3,  Topic 18
Message 38        Wed Sep 08, 1993
M.COLWELL1 [MattMan]         at 22:41 EDT
 
I used to use Novaterm 9.4, but it never seemed to chop the padding.  Even
when I told it to.

Now I use my bemmer (IBM) to call.  If wizard worked right, I probably use my
commie to call... oh well..

MattMan

 ------------
Category 3,  Topic 18
Message 39        Sun Sep 19, 1993
B.ECKARD                     at 08:16 EDT
 
I have two files that I d/l'd ed from Genie with    (for CS-DOS9 with      )
with the .LZH extension.  How t do I dissolve these program       files?  I
have CS-DOS but don't see anything that supports .LZH.  Can I dissolve these
files in Cp P/M mode (I have a .LZH decompressor    ion progrm am for that
mode). I am realatively new with CS-DOS so thanks for your help and your
patience wti  ith my questions! :/ )   
 ------------
Category 3,  Topic 18
Message 41        Wed Dec 29, 1993
W.WIESE [WES256]             at 12:29 EST
 
Am having problem with CSDOS and specifically [D [D [D [D [D [C [ [ [Cy LHA to
create SFX files to upload. Am using CSDOS v1.5 and LHA v1.2. After LHA loads
in the file to the 1750, and after it creates the SFX header to the 
destination disk, it locks up. The bar graph is there for  the load in to REU,
but when it's time to write the compressed file back out to the destination
disk, i get no drive activity. Any ideas????? Any help would be appreciated. I
also noticed this using arc128 also if source and destination are the same
drive. Setup is CMD HD and various floppys and expanded 1750 REU(in 1750
mode).
 ------------
Category 3,  Topic 18
Message 42        Wed Dec 29, 1993
C128.JBEE                    at 14:00 EST
 
 Are you using a flat C-128?
 ------------
Category 3,  Topic 18
Message 43        Wed Dec 29, 1993
W.WIESE [WES256]             at 23:08 EST
 
Yes,Jim I have tried it with 2 seperate flat 128's and also tried it with
nothing but the CMD HD on the serial bus-same results.I also had a chance to
try lhx and it will write the first file only from the archive then lock
up....totally befuddled on this one..... Whattya think, maybe otta go back to
using 4 128 roms instead of 2?....I don't think that's it, cause everything
else runs fine.... Just CS-DOS is giving me fits. :[
 ------------
Category 3,  Topic 18
Message 44        Mon Jan 03, 1994
C128.JBEE                    at 15:23 EST
 
 > W.WIESE [WES256]
 > Am having problem with CSDOS and specifically LHA to create SFX files
 > to upload.  Am using CSDOS v1.5 and LHA v1.2.

 If you have a 1581 disk drive, please let me know.

 IF you own a flat C-128, I would suggest trying to create the files by
 first turning JiffyDos off.  There seems to be a timing problem on
 flat C-128s while using CS-DOS/arc, with JiffyDos enabled, that hangs
 the serial bus.

 I create LHA/SFX files on the CMD HD using the same (any) partition
 everyday with no problem, using my C-128Ds.  But, it seems all the
 problems with the drives hanging are on flat C-128s.
 ------------
Category 3,  Topic 18
Message 45        Mon Jan 03, 1994
F.OGLE [Color BBS]           at 21:17 EST
 
I had problems using CSDOS on my flat 128 too ... It cleared up when I
switched to my 128D ...
 ------------
Category 3,  Topic 18
Message 46        Wed Jan 05, 1994
CBM-MARK                     at 08:37 EST
 
 CS-DOS seems to work just fine on my flat C128.  At least I haven't noticed
 any problem, as long as I use CS-DOS correctly that is ;>  The one problem
 I do have is a bad connecting REU which causes CS-DOS to fail.
 ------------
Category 3,  Topic 18
Message 47        Sun Jan 09, 1994
H.HERMAN1                    at 03:43 EST
 
Mark,

>I do have is a bad connecting REU which causes CS-DOS to fail.

And, so other software runs okey?  :/

Howie
 ------------
Category 3,  Topic 18
Message 48        Sun Jan 09, 1994
CBM-MARK                     at 20:26 EST
 
 Sure ;>  Other software runs just fine, Howie, as long as I don't plug in
 the REU.  If I do use the REU I have to run that Ram check program that
 came with the REU to make sure it's seating properly in the port.  But that's
 not fool proof either since moving the computer can, and has, unseated the
 REU :(  Strangely, I've never had problems with my swiftlink, but I'm getting
 off topic here ;)
 ------------
Category 3,  Topic 18
Message 49        Mon Jan 10, 1994
CBM-ED [e.g.bell]            at 05:15 EST
 
 Mark:  Someone makes a pencil type thing that resilvers the contacts
 of things.  Perhaps it might help with the card edge connector of
 your cart port.
 ------------
Category 3,  Topic 18
Message 50        Mon Jan 10, 1994
D.TUOMI [Doctor]             at 07:00 EST
 
The only problems I've had with CS-DOS is when I try to disolve a LH-ARC to a
CMD native mode partitions.  Doesn't seem to like that, it locks up everytime.

Doc.
 ------------
Category 3,  Topic 18
Message 51        Mon Jan 10, 1994
C128.JBEE                    at 16:04 EST
 
 > D.TUOMI [Doctor]             at 07:00 EST
 > The only problems I've had with CS-DOS is when I try to disolve a LH-ARC
 > to a  CMD native mode partitions.  Doesn't seem to like that, it locks up
 > everytime.

 What does your system consist of hardware wise?
 ------------
Category 3,  Topic 18
Message 52        Mon Jan 10, 1994
D.ROHNER                     at 23:49 EST
 
I have the same problem. Arc, LHA, and bvunzip, don't like the hd. They work
fine on C= drives. I have tried the suggestions to assign the partit ns and/or
set the output partition as default. What seems to happen is that it starts to
disolve and doesn't close the file and move on. I have a flat 128 and the hd.
 ------------
Category 3,  Topic 18
Message 53        Tue Jan 11, 1994
H.HERMAN1                    at 01:16 EST
 
Doc,

CS/DOS's LHA's run fine on RAMLink's native partitions.

My gripe is that the LHA's use the cs/dos clock to time themselves, and then
forget to reset the time of day when they are done.  I quess I should really
write a couple of short autoexecs to do the LHA'ing, and reset the clock at
exit.

Something else for me to do during those idle moments...

Howie
 ------------
Category 3,  Topic 18
Message 54        Tue Jan 11, 1994
C128.JBEE                    at 02:35 EST
 
 The one common thread is flat 128s with JiffyDos.  Have you tried
 creating or dissolving the archives without JiffyDos active (using
 the switch)?
 ------------
Category 3,  Topic 18
Message 55        Thu Jan 13, 1994
D.TUOMI [Doctor]             at 01:05 EST
 
I'm using a 128D with 2 1571's and an FD-4000 with a 1750 REU. CS-DOS doesn't
really seem to like the setup, I usually end up disloving onto one of the
1571's.  A fellow sysop who runs the local user group BBS complains of the
same problem with a 128 (flat) with CMD-HD and 1750 REU.

I've not tried to disable JiffyDOS completely yet.  I was hoping to not have
to, since having JiffyDOS does improve the speed slightly.  I'll give it a
try, though.

Doc.
 ------------
Category 3,  Topic 18
Message 56        Wed Feb 02, 1994
C128.JBEE                    at 06:23 EST
 
 >D.TUOMI

 Can I send you a disk with my setup to try?
 ------------
Category 3,  Topic 18
Message 60        Sat Feb 12, 1994
W.WIESE [WES256]             at 22:28 EST
 
Well got the flat128-lha/arc disk access problem semi-solved. If jd is out and
fast mode is in it works ok.If jd is in and fast mode is out it works ok.  I
tried this with all emulation types on my xpanded hd with the same
results.Setup is flat128-xpanded reu-xpanded hd.The problem must be chip
and/or software timing in the disk access routines within the csdos s/w and/or
the jd s/w ONLY in fast mode routines tho.
 ------------
Category 3,  Topic 18
Message 61        Wed Feb 16, 1994
D.TUOMI [Doctor]             at 04:57 EST
 
I'm still having the problem, and would definately appreciate a copy of your
setup disk Jbee.

Doc.
 ------------
Category 3,  Topic 18
Message 62        Wed Feb 16, 1994
C128.JBEE                    at 14:38 EST
 
 D.TUOMI [Doctor],
 Okay :)
 ------------
Category 3,  Topic 18
Message 63        Thu Feb 17, 1994
M.KIRBY2                     at 19:43 EST
 
Can anyone help me with CSXARC?  I load in the CS-DOC shell, then CSXARC but 
when I try De-arcing a file I always get a syntax error.
 ------------
Category 3,  Topic 18
Message 64        Fri Feb 18, 1994
C128.JBEE                    at 00:10 EST
 
 csxarc/x a:filename

 I think you leave off the ".arc" for CSXARC because it expects any .arc
 file to have the ".arc" already appended to the file name.
 ------------
Category 3,  Topic 18
Message 65        Fri Feb 18, 1994
M.KIRBY2                     at 03:31 EST
 
Tried that.  I get back:

searching for x a:filename

?file not found error

I tried the filename with and without the ARC suffix.
 ------------
Category 3,  Topic 18
Message 66        Fri Feb 18, 1994
H.HERMAN1                    at 05:18 EST
 
MK,

Try using CSARC instead of CSXARC.

CSX may (I am not sure) include some disk burst routines which will cough with
anything except a vanilla dos.  CSARC uses standard calls and should work with
all drives and dos's, such as JiffyDos, etc.

The syntax is the same.

Not sure if it matters, but I *always* tell cs/dos where to do its stuff. You
might want to do the same and include the drive designator as well:

csarc/xa a:filename.arc

Howie
 ------------
Category 3,  Topic 18
Message 67        Fri Feb 18, 1994
M.RANDALL2 [Maurice]         at 20:02 EST
 
Is it possible that the filename you are trying to access has lowercase ascii
characters in it? If so, you will always get a  file not found error. This is
because you can't type a lowercase ascii character from the 64 or 128 keyboard
unless the software supports it. From BASIC, it is impossible. CS-DOS will
also have this problem since it operates from BASIC. If this is the case, try
using some sort of utility to rename the file and try it again. I'd be willing
to bet that this is the problem.
 ------------
Category 3,  Topic 18
Message 68        Fri Feb 18, 1994
M.KIRBY2                     at 22:34 EST
 
THat was slightly better.  Nom some times it finds the file but then I says
"loading"  and the machine siezes up.  At first I thought it was taking longer
because  the file is very long (1163 blocks).  I can't even get a listing of
the files in the arc.   Could the fact that the File is on my RamLink be
causing trouble.
 ------------
Category 3,  Topic 18
Message 69        Sun Feb 20, 1994
H.HERMAN1                    at 02:40 EST
 
 MK,

 Just to touch on basics, have you correctly defined the REU area which
 cs/dos can use as a work area?

 I am referring here to the poking in the autoexec:

 poke 7120,2*16+5
 poke 7119,2*16+5

 Howie
 ------------
Category 3,  Topic 18
Message 70        Mon Feb 21, 1994
J.KIMMINAU [Doc K]           at 21:50 EST
 
  MK,
     Maybe this is way off line...but I just recently started
  de-arcing with CS-DOS, too.  I got the exact same problems as
  you describe for an entire night, using ARC2.41, CSARC ad
  CSXARC.  Eventual solution was to realize that the instructions
  (at least my copy of the docs) didn't tell me the obvious:
  the command to arc is not "arc filename" but, for each of the
  above, "arc128 filename" or "csarc filename" or "csxarc filename".
  Actually, the docs do show the correct command for csarc and
  csxarc, but I didn't pick it up for awhile because I was locked
  into using the command "arc" after reading the arc 2.41 instr.
     One other thing I did was install all the arc programs onto
  the ramdisk, but I don't think that solves the problem you 
  described.
      If it didn't help you, at least my experience may help 
  another new CS user.  Overall, its quite a good program.
      Doc K.
 ------------
Category 3,  Topic 18
Message 71        Tue Feb 22, 1994
CBM-MARK                     at 13:53 EST
 
 Yes, I'll bet that "ARC" vs "ARC128" threw the *majority* of new CSDOS
 ussers for a loop at first.  Me Included ;)
 ------------
Category 3,  Topic 18
Message 72        Tue Feb 22, 1994
CBM-ED [e.g.bell]            at 14:33 EST
 
 It seems to me that you can change the name of ARC128 to just ARC,
 install it in your RAMDISK, save your RAMDISK to disk so it is loaded
 with the renamed ARDC128, then in the future, you can just use the
 old ARC/# ##### ##### type format, if you were so inclined.  :)
 I do remember all the messages tho, on this problem, when Chris first
 uploaded the program. 
 ------------
Category 3,  Topic 18
Message 73        Wed Feb 23, 1994
M.KIRBY2                     at 10:31 EST
 
All suggestions appriciated but none of them did any good.
 ------------
Category 3,  Topic 18
Message 74        Thu Feb 24, 1994
H.HERMAN1                    at 03:31 EST
 
MK,

>All suggestions appriciated but none of them did any good.

Did you provide a description of your computer set-up, and peripherals?

This may help ID a problem source.

Howie
 ------------
Category 3,  Topic 18
Message 75        Sat Feb 26, 1994
M.KIRBY2                     at 00:15 EST
 
I have a flat C128, a RAMLink with a 1 meg simm plus a two meg REU divided
into  3 partitions (one is set aside for REUs) device number 16, A 1571 disk
drive 
 as device 9, and an Excel 2001 (1571 compatable) as device 8. And if makes
any diference I have a 1084 monitor, and a star NX-2420 with a G-Wiz 
interface.
 ------------
Category 3,  Topic 18
Message 76        Sat Feb 26, 1994
C128.JBEE                    at 01:23 EST
 
 Try doing a DCLEAR on each 1571 (#8 and #9) before creating the archives.
 ------------
Category 3,  Topic 18
Message 77        Tue Jul 05, 1994
J.STEPHENSO1 [Jimbo]         at 01:16 EDT
 
I've got a question about LHA compression.  I was under the impression that it
was the same for all platforms, but I ran into a snag last night.  I
downloaded an archive that had a bunch of SIDs that had been collected for an
Amiga SIDplayer.  After figuring out how to get past the path names (four
deep!), I was able to use LHX to decompress them, or so I thought.  I got a
CRC error for each one, and each one turned out to be unusable in the
SIDplayer I had lying around.  Has anyone had success dissolving Amiga .LHA
archives, and how did you do it?  Thanks,

Jimbo


Oh, yeah, another question while I've got your attention.  The docs for LHX
say that I need a 1750 to make a LHArchive, but I can tell it what banks it
can use.  Can I use a 1764 and just tell it to use banks 0-3? Thanks again.
 ------------
Category 3,  Topic 18
Message 78        Tue Jul 05, 1994
CBM-ED [e.g.bell]            at 07:29 EDT
 
 Jimbo:
  JS> Can I use a 1764

 When I first started I only had a 1764 and it worked, so I know that it
 can be done.  I believe there may have been a poke necessary, tho, as 
 you surmised.  It would be in the docs for CS-DOS though.  

 Also, as I recall, the docs say you can put an SFX header onto an LZH
 file and make it an SFX like that.
 ------------
Category 3,  Topic 18
Message 79        Tue Jul 05, 1994
G.RUTTER1                    at 22:01 EDT
 
Well here is another new CS-DOS user that's totally lost. I have downloaded
the 2 CS-DOS 1.5 files and the archived help files. I cannot get CS-DOS to
dissolve, so used O-Q to dissolve the 2nd file. It could not handle the 1st. I
read that file 9620 is needed to update the files, but cannot find it. I then
read that I need file 8223 to make it work, again cannot find it. I have a
flat C128, 1571, 1750 clone & FD2000 with Jiffy DOS. What files do I need to
dissolve archived files?     Thank you :)
 ------------
Category 3,  Topic 18
Message 80        Wed Jul 06, 1994
C128.JBEE                    at 03:35 EDT
 
 > J.STEPHENSO1

 If you are getting CRC errors most likely the LHA file is LHA-5, a newer
 version found mostly on Amigas.  The PC compression standards you can
 handle are .arc (older versions), .zip V1.10, and the older LHA.  You can
 not dissolve lha-5 or zip 2.04g.
 ------------
Category 3,  Topic 18
Message 81        Wed Jul 06, 1994
C128.JBEE                    at 03:36 EDT
 
 > G.RUTTER1

 If you have both CS-DOS .sfx files you just load and run them in C-128
 mode to dissolve them onto a blank disk.
 ------------
Category 3,  Topic 18
Message 82        Thu Jul 07, 1994
J.STEPHENSO1 [Jimbo]         at 01:50 EDT
 
JBEE - Ahhh, I see.  In order to attempt to unarchive them I used LHD and
redirected output to the printer.  Now that I think about it every single one
was LHA-5.  I had no idea there were different LHAs in use.  Thanks.

Jimbo

 ------------

 