🚀 go-pugleaf

Nik Zapantis writes:
>One of our users reported the following problem when he tried to run
>Uniterm ver 2.0a 20 with the Magic Sac connected to his ST:
>
>Configuration: 1040 ST with 20MB SH204 hard drive, Magic Sac+Translator box
>the Hard disk has 3 ST and 2 Mac partitions (created with Magic Sac).
>When he tried to use Uniterm 2.0a 20 (from floppy) when Uniterm came up it
>destroyed the Mac partitions on the hard disk (ST partitions ok).
>He recreated his Mac partitions but every time he run Uniterm the partitions
>were destroyed.
>He then switched back to Uniterm 1.8a20 and everything worked fine.
I find this VERY VERY VERY VERY VERY VERY VERY VERY VERY VERY VERY VERY
VERY VERY VERY VERY VERY VERY VERY VERY VERY VERY VERY VERY VERY VERY hard
to believe, UniTerm DOESN'T start itsself, it's  GEMDOS...., UniTerm doesn't
write to ANY disk without human intervention and you really want me to 
believe that UniTerm suddenly bypassed GEMDOS and just for pleasure used
a BIOS call to destroy those nasty Mac partitions (and I can assure you
UniTerm uses GEMDOS for all disk operations) (oh yes and changed the 
current drive by itsself aswell.......). 

                                   Simon Poole

                                   Bitnet: K538915@CZHRZU1A
                                   UUCP: ....mcvax!cernvax!forty2!poole

PS: I know this wasn't very helpful, but computers sometimes do strange
    but not THAT strange!