SYSTEM@UVPHYS.BITNET (NIK ZAPANTIS) (03/05/88)
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. Does anyone know ( Simom??) why Uniterm 2.0a 20 cannot coexist with the above hardware set up? Nik Zapantis UVic, Physics Victoria, BC V8W 2Y2 (604) 721-7729 system@uvphys.bitnet
dsmall@well.UUCP (David Small) (03/06/88)
In the base note, Nik Zapantis asks if there's any known incompatability between Uniterm and the hard disk under Magic Sac. I don't believe there is; without further details, it's hard to know for certain. The only bugs I know of that have been reported in the hard disk implementation are that a) Finder/Systems above 5.4/3.2 should not be used (possible disk damage report), and b) filenames longer than 21 characters cause problems under an HFS hard disk, and can damage the directory structure. In short, I would think at first glance the problem isn't Uniterm, but rather a long filename or too recent a Finder/System. However, murphy's law always applies, especially at dP. Thanks, Dave Small / dP etc / My opinions are my opinions.
poole@forty2.UUCP (Simon Poole) (03/06/88)
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!