Falcon maintenance: Phantom&CT60e

[Steve]

If the Falcon is working 100% in 030 standard and accelerated then the issue will be either a ct60e/SV hardware/software issue.

Firstly I recommend take the SV out and just focus on the ct60e for now.

* Are you running the latest firmware?
* Are you running with NVDI (required)

Also: power supply is massively important. My ct60e is VERY picky about the PSU. Do you have different supplies you can test.

[qq1975b]

Hi,

It has v.1.03c (ABEv5M,SDRv5E).
Without the SV it happens the same.

I have a low profile Pico PSU (120W):

https://www.amazon.es/Mini-Box-picoPSU- ... B005TWE3O8 (Mini-Box picoPSU-120 - Fuente de alimentación ATX (12 V-DC/DC))


I didn't know it was a difficult choice....

[Steve]

Ok leave the SV out till the problem is solved. I'd keep the bios the same don't mess around with it.

Try a different PSU first. And make sure NVDI is the ONLY thing in auto folder. Rename cops/xcontrol or temporarily move them in case you have a rogue 060 incompatible extension.

[mikro]

That reboot sounds very scary, that isn't a symptom of anything "known". So yes, take the SV away and do a *thorough* testing in 060 mode (and compare to 030 mode). In your previous post you describe stuff on HDMI, on some occasion you can get white screen with the cursor "making its way in the white" if the SV_XBIOS isn't present.

Phantom, if not enabled, doesn't have any effect on the machine (if installed properly, of course).

I would basically start with everything removed, even floppy and hard drive.

[qq1975b]

I have pulled out the SV and let only NVDI and WDIALOG in the Auto folder. Then I disabled all CPX. It booted OK in the first attempt. I tested it several times and all OK. The only issue I have found is that the keyboard doesn't work very well. I mean that sometimes a key seems to be stuck when I think it isn't or the space bar, for example, it is difficult to make it work.

By the way, is there any prg to test the sound? I mean to test that is stereo. I entered in the audio setup but moving the balance to left/right doesn't change anything like I think any other parameter (treble/bass).

I will put SV_XBIOS again in the auto folder and see how does it work with the SV. Maybe was a CPX compatibility problem.... Is the order the following?

NVDI
SV_XBIOS
WDIALOG

Thank you.

[Steve]

Great! Glad you're getting there. Hopefully @mikro can comment on the SV driver order. Or there surely must have been a thread about it in the SuperVidel forum section of Atari forum, with a little search.

In regards to your keyboard it is very likely your internal keyboard cable has a fault - my Falcon keyboard had a fault & I had to replace the connector. To diagnose have the Falcon case open, move the keyboard around to flex the wire and see if it triggers the problem, then you know it's a cable issue - most likely is.

In regards to audio I'm not sure off the top of my head. Hopefully someone can chime in on that.

[mikro]

As per the manual...

5.1SV_XBIOS.PRG
Run this first in the auto folder.

I would leave WDIALOG.PRG out of equation for now.

As for sound, if you can't test any demos / mod files, you can still make a WAV file in Audacity or similar with interleaved muted channels. Or maybe even download it from somewhere, just google for it.

[qq1975b]

I have run SDMATEST and I listen a cracking noise :(

[mikro]

Please focus on one issue at time. If you're jumping between 060 / SuperVidel / clockpatch issues back and forth, nothing gets resolved.

[qq1975b]

Yes, sorry. I made a quick test on all 4 levels (030, Phantom, 060, SV) and messed it all, but I would like to start from 030 and then the following one by one.

For now I am just running the test cartridge and I will focus on 030 mode to detect any failure there.