| |
Monte Carlos
Registered: Jun 2004
Posts: 358 |
Error message: "Found more than one drive on IEC bus" with C128D metal and recent demos
Sorry for this lamer question. I use an C128D(metal), currently (although i have used C64 for years until i got room problems with the complete setup).
I have attached a 1541 ultimate and changed the internal 1571 drive to device no 10 by cutting the solder pads. The ultimate has dev no 8. This way i can watch many, mostly old, demos with 1541U. However, the most current demos always complain about more than one drive being enabled. Ok, i thought, plugging off the internal 1571 from the mainbord should fix the problem. I was wrong. The loaders still complain about more than one drive.
Am i wrong with my understanding that plugging off the internal drive also disables the ATN signal? |
|
... 34 posts hidden. Click here to view all posts....
|
| |
Krill
Registered: Apr 2002
Posts: 2969 |
It executes a BRK if there's an error, such as device not present. Have you changed "lda #9 ; device number" to #10 for your setup? |
| |
Monte Carlos
Registered: Jun 2004
Posts: 358 |
Ahh fuck,sorry! |
| |
Monte Carlos
Registered: Jun 2004
Posts: 358 |
So now some good new:
I tested FLT K9 orange with three settings and displayed active drives beforehand. Drive 8 = 1541u, drive 11=1571:
1.) No script ran -> Drive 8 and 11 shown as active.
Demo loader outputs error message that more than one drive is on the bus
2.) Ran script "OPEN 1,11,15,"M-W"+CHR$(119)+CHR$(0)+CHR$(2)+CHR$(0)+CHR$(0):CLOSE 1" to disable drive 11 -> Only drive 8 shown as active. Demo loader does not output error message but instead just hangs up.
3.) Ran Krills script -> Only drive 8 shown as active. Demo loader works perfectly.
I now created a folder 0_scripts in the base dir of the 1571U and put all those successful and unsuccessful code attemps into a d64 in this folder. This way i can quickly disable the internal 1571 before running any demos.
As remarked by Skate, the d64 should be mounted before running any contents. If they are run directly, you will not receive the "ready." prompt after code has been run. |
| |
Krill
Registered: Apr 2002
Posts: 2969 |
Okay, cool, but do both variants work nicely, with and without "tightloop" enabled? :) |
| |
Monte Carlos
Registered: Jun 2004
Posts: 358 |
I did not test this up to now. Currently tightloop = 0. |
| |
Monte Carlos
Registered: Jun 2004
Posts: 358 |
Tightloop = 1 also works fine. |
| |
Krill
Registered: Apr 2002
Posts: 2969 |
Alright, great, thanks! I guess i'll also post this on Codebase64 on a boring Sunday or so, since this is a problem that many people might face. |
| |
Monte Carlos
Registered: Jun 2004
Posts: 358 |
In common it would be interesting to silence all but one drive before irq-loading sth and then awake drives again after loading or at the end of the production. |
| |
tlr
Registered: Sep 2003
Posts: 1787 |
Nice work here! I second the "awake" bit. Not entierly trivial. Some kind of more advanced port knocking I guess. Maybe it's sufficient with a sequence of well timed ATN toggles? |
| |
Krill
Registered: Apr 2002
Posts: 2969 |
Yes, this is the hard part and one of the main reasons i haven't added this to former releases of my loaders. |
| Previous - 1 | 2 | 3 | 4 | 5 - Next |
