by I have come across a * bug which seems to cause a print overrun
when I run my my batch file from Gulam, my favorite ST shell, from my
1040 STF. This problem occurs in *all* 3 versions of Gulam that I
have: 1.00.00.xx, 1.03.04.05 (121887), 1.03.05.05 (03xx88) (I don't
have the actual numbers in front of me :-) Here's the batch file. If
someone can see an error in it, I'd love to hear about it.
echo " Disk: $-n" >prn:
# cat a:\diskid.qqq > prn:
echo 'n' >prn:
foreach file { a:\...\*.arc }
echo $file
echo Verbose listing of $file : >prn:
echo ' ' >prn:
c:\arc\arc -v $file >prn:
echo ' ' >prn:
echo '...'
sleep 8
endfor
This little procedure will print out a verbose listing of one of my
ARChive disks. Normally, after a certain number of files are listed,
I get a -35 error. After that Gulam can't find anymore files on any
disk!! Leaving to the desktop and reentering Gulam does not help; it
doesn't even find gulam.g in the same directory. And once, coming
back to the desktop, there were "0 Files" in all my windows!
It seems that some system tables somewhere were overridden. The only
solution is to reboot, a warm boot suffices! By the way, in my
C:\AUTO\ folder I have ETRNL2, ACACHE, FATSPEED, and GEMBOOT. Would
any of these have an interaction? If I remember correctly, FATSPEED
does do some patching for print redirection also.
Thanks.
--
Ralph P. Sobek Disclaimer: The above ruminations are my own.