CPCWiki forum

General Category => Amstrad CPC hardware => Topic started by: SerErris on 17:37, 14 September 20

Title: Looking for VDOS 2.0-X for CPC464
Post by: SerErris on 17:37, 14 September 20
Hi,


I have found a VDOS 2.0-X online that works great with a 6128. However I have a 464 and want to have it as an extra ROM (esp. for the |XMON). So I used it on the CPC464 as well, but the XMON (and |fast as well) do not work with 464.


In XMON you cannot see anything (blue screen), but it is full alive. If you exit and enter |slow, you can see everything again.


So there must be something in the ROM I have, that is not compatible with the CPC464 ROM. It is just a minor thing, but makes the XMON unusable.


So does anyone have a copy of VDOS 2.0-X for the 464?


I had one in 86, but neither the CPC464 nor the X-Module or the F1-X exists anymore (not to my knowledge :-) ).
Title: Re: Looking for VDOS 2.0-X for CPC464
Post by: Gryzor on 19:23, 14 September 20
So many unknown words here, I'm embarrassed.
Title: Re: Looking for VDOS 2.0-X for CPC464
Post by: SerErris on 15:37, 15 September 20
Sorry, I was not trying to embarrass anyone ...  ;D


It is just a very specific topic and if you never had a Vortex X-Drive you most likely never come across of any of those. So don't be embarrassed ... no reason to  :-*
Title: Re: Looking for VDOS 2.0-X for CPC464
Post by: botfixer on 18:58, 24 September 20
Yes, i think i have one. I have a 5,25 Drive with an external Controller. I used it with Standard Amstrad ROM, because using it as 3,5 Inch Drive on my CPC  :D


I put the Vdos ROM out, no need for that at this time.


It´s hard to find, but i have it. I have to go digging.
Title: Re: Looking for VDOS 2.0-X for CPC464
Post by: GUNHED on 21:19, 24 September 20
Well, just to inform you... the Vortex ROMs are protected by hardware.

If you 'just' copy the EPROM it will not work in an non-Vortex controller.

Of course there is a decoeded verson of the F1-X VDOS for the CPCs too.Didn't I upload this working decoding version years ago?
Title: Re: Looking for VDOS 2.0-X for CPC464
Post by: GUNHED on 17:03, 28 September 20
I found the VDOS 2.00 which I did upload... see there...
http://cpcwiki.de/forum/index.php/topic,612.msg4753.html#msg4753
For some reasons I can't upload here.
Title: Re: Looking for VDOS 2.0-X for CPC464
Post by: SerErris on 09:29, 12 August 21
Coming back to it. I found another version (which is 2.0-X Version). That works.

The 2.0-X Version does have an internal debugger (monitor) build in.

However the version I have does only work with a 6128 configuration (tried in winape). Using 6128 ROM + Basic 1.1 and AMSDOS it works. But using it with 464 + BASIC 1.0 and AMSDOS does not execute the |xmon correctly. I do not understand where the difference is and if they really programmed a XMON specifically for the 6128 and one for the 464 ...

So the attached version is it - but as I said it only works with a 6128 configuration.
Title: Re: Looking for VDOS 2.0-X for CPC464
Post by: GUNHED on 13:56, 12 August 21
Du kannst ja den XMON Teil disassemblieren, und die Einsprünge in dir Firmware von 6128 auf 464 umstellen. Das 'Große ROM Listing' könnte dabei helfen.
Title: Re: Looking for VDOS 2.0-X for CPC464
Post by: SerErris on 21:40, 19 February 22
I think I am going to approach that now. Sounds like a great learning experience.


I think, that it might be the |fast routine, that does not work at all and is probably used by |xmon
Title: Re: Looking for VDOS 2.0-X for CPC464
Post by: SerErris on 20:56, 25 November 22
@GUNHED .. do you have by chance the descrambling algorythm available ? 

The M1 cycle (do not scramble) and non M1 cycle drive my crazy in terms of what logic I need to apply. 
Title: Re: Looking for VDOS 2.0-X for CPC464
Post by: GUNHED on 18:11, 27 November 22
Sadly no, I had a talk about it 20 years ago, but sorry, too long ago.
Would be great to have a descrambler, for all Vortex DOS ROMs.
Title: Re: Looking for VDOS 2.0-X for CPC464
Post by: SerErris on 18:16, 27 November 22
Yeah .. I currently have not other idea than dissassembling the rom. This is definately not a simple thing as all the data blocks needs to have special handling and all the code blocks as well. And you definately need to know where real code is and where the routine start are. So that is quite painful.
Powered by SMFPacks Menu Editor Mod