| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2653.1 | an update | FSCORE::KAYE | He who dies with the most toys is dead | Fri Jul 28 1989 22:16 | 14 |
| I got my hands on another 2000 with an internal Miniscribe. I hooked
my 2 Seagates up to his 2090A and tried again. It worked
a little better than mine, but gave me the same 'bad floppy' stuff at
#4, instead of the first floppy. I tried swapping his 2090A into mine,
but nothing changed. I called Commodore (Canada) and they sent me a
new ROM for the 20290A (cus the new 2090A's were different than the 1
i had). It came today, but didn't change the problem (hopefully it
will fix the problem of not booting accasionaly). In the USENET in 1
of the notes about NOCLICK was a reference to a problem with
TRACKDISK.DEVICE and raw reads and writes. I assume that Quarterback
uses raw reads and writes cus it bypasses AmigaDos and writes it's own
format. Anyone know what the problem with TRACKDISK is?
mark
|
| 2653.2 | An OS bug... | FRAMBO::BALZER | Christian Balzer DTN:785-1029 | Mon Jul 31 1989 04:29 | 8 |
| Re: .1
The RawRead/RawWrite problem is an OS bug to be fixed in 1.4 or
an intermediant SetPatch release. See the various PC-Patch, PC-Copy
topics for some more details.
<CB> (slightly feverish, but still at work)
|
| 2653.3 | DPIII/2090...Aaaarghh | GIDDAY::LAWSON | | Thu Aug 02 1990 19:33 | 18 |
| I dont know wheter or not this is going in the right topic but here
goes... (also, let me preface this by saying that I'm not sure my
investment in an A2500 was all that good an idea, given the general
flakiness of various bits of software....)
However, when using DPIII in hires overscan AND reading/writing to
hard disk, I get the disk access led on and depending on how frustrated
I get (by clicking mouse buttons etc) I get various symptoms, non of
which do much for my state of mind. I need this facility because Im
trying to drive a polaroid palette. ) or at least I think I do.
I tried 2090patch.zoo. Did it as per instructions and then spent the
remainder of the night rebuilding my hard disk (Not a Dos device!!!)
Maybe I got a bad copy. Any suggestions?
Glenn
|
| 2653.4 | Swapping Screens | TLE::RMEYERS | Randy Meyers | Thu Aug 02 1990 21:34 | 21 |
| Re: .3
> However, when using DPIII in hires overscan AND reading/writing to
> hard disk, [problems occur with the 2090 disk controller]
Sigh! The guy who invented the FlixerFixer use to do what you are
doing as a test of Commodore's 2090 patches. The FlixerFixer folks
use to (maybe still do) encourage people to use overscan screens
since the FlixerFixer can handle it. However, they started getting
complaints that the FlixerFixer broke disk I/O. Of course, the
FlixerFixer was causing no problems: the overscan screen was just
revealing the DMA bug in the A2090. Anyway, every time Commodore
would patch the 2090 driver code, the FlixerFixer inventor would
fire up dpaint in overscanned mode and try and load or save
a file. Usually, the experiment would show that the 2090 still
had problems.
There is a workaround you might try. When you need to do disk I/O,
use the Amiga-M and Amiga-N keys to swap the overscanned screen for
the Workbench screen as soon as the disk I/O starts. This will allow
the 2090 a clear shot at memory.
|
| 2653.5 | WHat is Commodore doing about this? | GIDDAY::LAWSON | | Sun Aug 05 1990 19:20 | 12 |
| Thanx Randy..I'll give it a try....
BTW, Does anyone out there know what the official C= attitude is WRT this
problem? This is still under warranty and I feel that they might want to
fix this somehow, like maybe swapping the 2090a for a 2091???
I phoned the local C= tech support people and got a "uhhh?" I
interpreted this as either a) ignorance or, b) toeing the party line
(nothing wrong with OUR kit!)....not encouraging.
Cheers,
Glenn
|