| | 6R6
Registered: Feb 2002
Posts: 245 |
Drive Code C128D N0SD0S Scanner bug.
Recently Nostalgia released Legacy of the Ancients.
Legacy of the Ancients +8DIR
The program used to scan the IFFL file refuse to
work on a C128D. I got this error report from someone
in USA, so I did a test on my own C128D.
What happens is:
Installer searches for the iffl file,
then it locates track+sector of the iffl file.
At this point this text is displayed on screen.
N0SD0S V1.2
SCANNING
73, CBM DOS V3.0 1571,00,00
Then scanner get installed in the 1571 drive. Scanner now
searches the IFFL file and you can hear the drive is working
as it makes a click for each track it moves to.
But then at the end of scanning everything freezes,
drive is spinning forever and the led is on.
I tried the same game disk on my c64+1541 and it
works fine. I tried not messing with the $1c07 timer.
I tried with and without fastload cartridge on my c128D.
But I get the same bug each time. Some have said i Have a bad VIC chip, but the VSP scroller in the n0s intro works fine for me.
I am not sure if its the C128D or the disk drive that is causing the problem. I wonder if anyone of you can help
me by verifying if it works or not on these setups:
1) C128D.
2) C128D but run the game from a external 1541(II) drive.
3) C128 + 1571
4) C128 + 1541(II)
5) C64 + 1571
Please post your report here.
Also, if you have any other suggestions to what
the problem might be please post here.
Thanks!
|
|
... 21 posts hidden. Click here to view all posts....
|
| | Ninja
Registered: Jan 2002
Posts: 411 |
GRG: Do you use ROM for moving the head? If not, have you tried raising the delay value for the movement?
|
| | TNT
Account closed
Registered: Oct 2004
Posts: 189 |
ninja: he seems to be using job code $e0. |
| | 6R6
Registered: Feb 2002
Posts: 245 |
Hello again,
Yes I'm using jobcode $e0 to move head.
Can you dump your C128D drive roms for me ?
You can use this tool I made:
Drive Memory Dump v1.0
This tool will print dos version number from
the error channel.
Please use that as filename.
Example filename:
"1541 dos v2.6"
Thanks and
Cheers!
Glenn
|
| | Mace
Registered: May 2002
Posts: 1799 |
Okikdoki. |
| | 6R6
Registered: Feb 2002
Posts: 245 |
( My C128D 1571 drive freaking out on Lota )
I did some more checking, and I found out that
the scanner freaks out somewhere between track 32-33.
If I exit the scanner when reaching track 32 the game
will load and run as it should.
Scanner checks the tracks in this order:
17,16,15,14,13,12,11,10,9,8,7,6,5,4,3,2,1
18,19,20,21,22,23,24,25,26,27,28,29,30,31,32, * freak out *
The lota game has game data in track 18.
(Not in bam t+s 18,00 and dir entry 18,01.)
lda $0a
cmp #32
bne more
jmp $c194 ;Exit scanner
badly aligned drive ? hmm..
Thanks to the ones who has sent me drive roms.
Currently I have:
3 * 1541(-II) roms (all different)
CBM 1541 64'er (73,64'er dos v3 1541,00,00)
CBM 1541 Digidos (73,digi-dos 1.0 1541,00,00)
CBM 1541 Dolphindos 2 (73,dolphindos.2 1541,00,00)
CBM 1541 Jiffydos 5 (73,jiffydos 5.0 1541,00,00)
CBM 1541 Speeddos ++ (73,speeddos ++ 1541,00,00)
CBM 1541 Speeddos 2.7 (73,speeddos 2.7 1541,00,00)
CBM 1541 Prologic System (73,Prologic Classic,00,00)
CBM 1541 Turbo Process System (73,turbo-access r2.8,00,00)
Oceanic 118 (73,cbm dos v2.6 1541,00,00)
Oceanic 118 (73,r-dos 40 tr. 1541,00,00)
3 * C128D 1571 roms (all different)
CBM 1571 (C128DCR) (73,cbm dos v3.1 1571,00,00)
CBM 1571 Jiffydos (C128D) (73,jiffydos 6.0 1571,00,00)
CBM 1581 (73,copyright cbm dos v10 1581,00,00)
CMD FD-2000 (73,cmd fd dos 1.40,00,00)
CMD FD-4000 (73,cmd fd dos 1.40,00,00)
And two versions of CMD HD v1.86 and v1.90, i havent had the time to check them.
These modified 1541 roms wont work with the current
n0sd0s identifier:
CBM 1541 Prologic System (73,Prologic Classic,00,00)
CBM 1541 Turbo Process System (73,turbo-access r2.8,00,00)
Mail me your roms if you have anything else.
Anyone have a CMD HD for sale ?
GRG |
| | Krill
Registered: Apr 2002
Posts: 2980 |
You're not running the thing in 2 MHz, are you?
Because in the 2 MHz mode, you must not use clv:bvc * for the byte sync but instead, poll $180f. The clv:bvc * method freezes once in a while.
But then, 2 MHz are really unnecessary for a scanner. However, they're not for loading. |
| | 6R6
Registered: Feb 2002
Posts: 245 |
@krill: My code doesnt use the register for 2mhz mode. But thanks for the info. |
| | MagerValp
Registered: Dec 2001
Posts: 1078 |
I'm leaning towards bad drive alignment, where it gets bad data at track 32 and up. Have you tried modifying the scanner to send over sector checksums one sector at a time?
|
| | 6R6
Registered: Feb 2002
Posts: 245 |
A friend of mine tested on 2 different C128D's some time ago, he had no troubles...
He also said that running the game on a c128d from an external 1541,1571 and oceanic (device #9) didnt work.
Didnt even show the dos error message (73,cmd dos v2.6 1541,00,00).
A c128d is just troubles.. RR-net doesnt work on it either...
@magervalp:
I will have to try that now. |
| | 6R6
Registered: Feb 2002
Posts: 245 |
Quote: C128 + 1571 : game loads
C128 + 1541-II: game loads
C128 + 1541 : game loads
C64 + 1571 : game loads (even using Final Cart. 3)
[edit]
I thought my C128D was broken, but the C64 mode still works, so:
C128D + internal: game loads (!!)
C128D + 1541-II : crash *)
*) with internal 1571 on, loading from external 1541-II, the light of the internal drive remains on and the game crashes with EOA logo. The DOS versions on the screen is 1571, while I load from 1541-II. Mind you, there's a device-# conflict...
@Mace:
Can you test LOTA with a normal C128 + various drives as device #9 and see if it hangs ?
@others:
Other games with N0sd0s has similar
problems running from device #9 on the C128D.
Tests has give these results:
C128D + 1541-II (device #9) : hangs on scanning
C128D + Oceanice (device #9) : hangs on scanning
C128D + 1581 (device #9) : works
Loading game from C128D disk drive, then switching device number to 9 ( 1541-II ) gets past scanning, then the EOA logo appears and game hangs.
In general there is a problem with using C128D and 1541-II drives on Device #9.
More to follow..
|
| Previous - 1 | 2 | 3 | 4 - Next | |
