1
Classifieds / Re: Wanted: 20 MB (or more) MFM hard disc
« Last post by Bryce on Today at 10:51 »Were there 3.5in MFM drives? I though they were all 5.25in or 8in.
Bryce.
Bryce.
The ultimate Amstrad CPC community!
News:
Recent Posts
2
Amstrad CPC hardware / Re: [HELP] CPC6128 Black screen after +12V accidental "injection"
« Last post by Bryce on Today at 10:47 »Another one saved!!!
BTW, someone raped a 1084
Actually it's the rebadged Highscreen version of the 1084. It was sold by a German electronics chain back in the day.
Bryce.
3
Games / Re: The World War Simulator Part II (zx/cpc)
« Last post by reidrac on Today at 01:38 »I enjoyed playing this.
I was surprised by the 100 % ending screen, I won't spoil it, however I will warn you it's not kid friendly as contains adult content.
Do you mean besides the explicit violence that is the main core of the game? It is OK to kill people while they sleep as long as they're historically proved bad people, but some 8-bit nudity is not family friendly. It probably doesn't matter.
I like how the game looks (although the graphics are a bit better on the Speccy; perhaps is the higher resolution), but not that much the concept. I guess I'm getting old
4
Hardware related / Re: 6128 glitching out (memory issues?)
« Last post by llopis on Yesterday at 23:19 »I improved my naive program to write random bytes 1KB at a time and compare against values in Bank 0. Surprisingly, it passes without detecting any errors.
(Yes, I know it's a dumb program to write in BASIC because it's so slow, but I didn't remember the ROM calls for printing strings).
Any idea what might be going wrong? Is the logic of my test wrong? Everything else seems to detect something wrong with Bank 1, so clearly I'm missing something. Well, doh, I just saw the incorrect data check! Re-running... <blush>
Edit: Yeah, it's failing right away. Yay!
(Yes, I know it's a dumb program to write in BASIC because it's so slow, but I didn't remember the ROM calls for printing strings).
Any idea what might be going wrong? Is the logic of my test wrong? Everything else seems to detect something wrong with Bank 1, so clearly I'm missing something. Well, doh, I just saw the incorrect data check! Re-running... <blush>
Edit: Yeah, it's failing right away. Yay!
5
Technical Support / Re: Power lead for 3.5" second drive.
« Last post by zeropolis79 on Yesterday at 23:11 »It's part of the casing.
6
Games / Re: The World War Simulator Part II (zx/cpc)
« Last post by Phantomz on Yesterday at 21:58 »I enjoyed playing this. 
I was surprised by the 100 % ending screen, I won't spoil it, however I will warn you it's not kid friendly as contains adult content.
I was surprised by the 100 % ending screen, I won't spoil it, however I will warn you it's not kid friendly as contains adult content.
7
Amstrad CPC hardware / Re: [HELP] CPC6128 Black screen after +12V accidental "injection"
« Last post by VincentGR on Yesterday at 21:38 »Another one saved!!!
BTW, someone raped a 1084
BTW, someone raped a 1084
8
Programming / Re: [cpctelera]Bit Arrays
« Last post by Arnaud on Yesterday at 21:05 »1/ ¿Where to go form here? I mean, how to convert this 'level.txt' into 'level.c' and 'level.h' and unexomize data on the fly?Exactly, rename level.txt into level.h. include it into your code and deflate the array of compressed data to free memory area
2/ I understand is necessary after level compression and exomization, to re compile project with new compressed 'level.c' and 'level.h' something like > 'make clean' > 'make cleanall' > 'make', am I correct?Yes, because new source files are generated and need to be compiled to make an executable
3/ Does @Arnaud approach work the same way? It seems to require a 'level.bin' file, automatically converted in 'level.c' and 'level.h' after compilation.Yes this the same way, the automatic convertion of cpctelera bin to c is used, that all.
Once again sorry for the delayed comment, please feel free to delete it if it's not appropiate.No worry of that
And a new cpcretrodev contest is a good time to code.
10
Hardware related / Re: 6128 glitching out (memory issues?)
« Last post by llopis on Yesterday at 18:55 »Did you test the whole range or only one address ? If you tested whole range, did you use the same patter for all location ?Good point. My test naively wrote the same bit pattern to all addresses. I'll change it to write different ones depending on the address.
My test does 2 pass
- one that fill the banks with bank unique value (fast, but will miss addressing error).
- the second that use a pseudo random pattern that will make sure that addressing error will be detected.