[comp.sys.atari.st] HDSCAN problem.

poirot@inria.inria.fr.UUCP (04/06/87)

Todd,

 Excuses me for writing to you via the net, but i'm not able to reach you
directly.

 I tried to use HDSCAN (1.121) posted recently on comp.sys.atari.st. I dont
remember exactly the date of the posting but it was near 04/04/87. This 
posting was in 3parts (2 for the program, 1 for utilitys..). 

 When i edit the program, i notice that there was not any ~ (tilde) chars.
But spaces were replaced by `. So i dont do any modification and after having
concatenate the 2 parts, go to transfer it to the ST (via kermit). Then i
uudecode it , using Dumas uudecode, with no errors, and finally de-arc it
with no problem too.

I do the same job with hdrs_othr.arc succefully.

 So i double click on HDSCAN12.PRG. The main screen came right. The ? prompt
was blinking. And then the problem appeared: I typed A (i tried either B 
and N with the same results). The program began to "access" drive A, and
then "access" Hard disk (access light blinking) and then a screen appeared
full of garbage (like if you try neochrome on a mono screen). The program
continue accessing the Hard disk during 3 or 4 seconds (My god, what can it
do ??),and finally the system go blocked (no bombs). 

RESET.

So, is it the posting that it 's bad ? Or can i try replace ` by spaces ??

Have you already got the problem ? Help needed. In the seeing of the main 
screen , it seems to be a very useful program, i want need it...

Disclaimer: Opinions expressed above do not necesseraly reflect those
	    of my Employer. I have no affiliations with any named company .

=============================================================================
Didier POIROT                                        D. Poirot
				
UUCP: ...!seismo!mcvax!inria!poirot                    INRIA
                                                  Domaine de Voluceau
                                                       B.P 105
                                                 78153 LE CHESNAY CEDEX
                                                       FRANCE
=============================================================================

trb@stag.UUCP ( Todd Burkey ) (04/08/87)

In article <8704061401.AA06934@inria.inria.fr> poirot@inria.inria.fr (Didier Poirot -- SPIT) writes:
>...hdscan 1.21..
>posting was in 3parts (2 for the program, 1 for utilitys..). 
>
This was the version I posted myself...at least I am getting stuff out
now!

> When i edit the program, i notice that there was not any ~ (tilde) chars.
>But spaces were replaced by `. So i dont do any modification and after having
>
This was the result of the uuencode that came with my Symmetrics...if
you didn't substitute them with spaces and the file unarc'ed ok, then
I am pretty sure your uudecode worked ok.

>then "access" Hard disk (access light blinking) and then a screen appeared
>full of garbage (like if you try neochrome on a mono screen). The program
>continue accessing the Hard disk during 3 or 4 seconds (My god, what can it
>do ??),and finally the system go blocked (no bombs). 
>
Actually, during that 3-4 seconds, the entire hard disk contents are
read into the program memory. I have no idea what would cause it to
garbage up and hang unless it is something to do with 1) the screen
codes on overseas systems being different (I use the vt52 esc codes a
lot in the program...and a few vdi calls for graphics and blitting) or
(and?) 2) the keyboard key values being different (I do a Bconin() and
use both the high and low words.) I logged into another unix system
and downloaded my post, uudecoded it, and unarced it the other day and
everything ran fine on both mono and color ST's...

I will look into the fabulous docs on the ST and see if I can find out
what the differences might be between US and overseas systems...

A note. If anyone else has problems with this or other programs people
post, you might want to include the system configuration, and any info
you might feel is pertinent (i.e. running big accessories, whether you
have had to bounce your system much lately to get it to work, etc) for
the authors' benefit...that way we can see if a pattern is developing.

-Todd Burkey
...ihnp4!meccts!zeke!stag!trb (use a full path, since trb@stag isn't
                               registered yet)