Jump to content

Zzalg_Repus

Members
  • Posts

    29
  • Joined

  • Last visited

Contact / Social Media

Profile Information

  • Location
    Germany

Recent Profile Visitors

3,626 profile views

Zzalg_Repus's Achievements

Space Invader

Space Invader (2/9)

7

Reputation

  1. Hey there! Just my two pennies: I'm using an original Raspberry 3 PSU (5.1V, 2,5A) with no problems at all. Maybe it's that extra tenth of a Volt that does the trick. IIRC, some PIs won't work reliably with a generic 5V PSU. SD Cards I've been trying so far with great success (685 kb/sec): SanDisk Ultra 16GB, Class 10 Transcend 16GB, Class 10 This is an excellent and and very reliable device. ?? Best, Frank
  2. Hey there! I'm just a recent user of the SDrive Max (coming from/still using several SIO2SDs) with firmware V1.2. It's all working great, except for the TURBO tape option, which just crashes the SDrive Max when enabled - it's "Sync Wait..." forever. No "Baud", "Length" or "Gap" numbers. Regular Tape-Emu (600 Baud) works fine, except that you cannot "Exit" a loading tape file properly - the display gets garbled and the SDrive gets unresponsive, while still loading the "tape". (Note the "DA:<empty>" prompt). Can somebody reproduce this with V1.2 and is does this actually work with lower firmware versions? Cheers, Frank
  3. I just thought, going back to my original post, that leaving a disk in a drive other than DSK1 might cause problems loading certain programs. I seem to remember this from BITD with some A8/C64 games (C64 especially), where an active second, third ... drive would cause problems with copy protections, though I never experienced that myself on any machine. (As an answer to myself: I *always* have "VOL1" in DSK3 - but then again there ARE some programs/games that won't run, but that's probably not because of having three active disk drives.) Thanks, guys, for all your comprehensive replies!
  4. I have an F18 V1. And I don't think this is intentional. What does CATALOGUE actually show when a disk drive is unmounted? Maybe this is an issue with the CF card? So far I haven't had any luck with CF cards, except for the one which came with my Nanopeb (at 128mb not *that* big). Has anyone have ever tried an SD to CF card adapter?
  5. Hey guys! I just encountered a strange bug with my Nanopeb - the command "CALL UNMOUNT(x)" does not work. For me, it just MOUNTS the volume specified in the specified drive, so CALL UNMOUNT(1) will actually MOUNT Vol#1 in drive 1. CALL UNMOUNT(2) will mount Vol#2 in drive 2, CALL UNMOUNT(3) will mount Vol#3 in drive 3. Can anybody reproduce this? Or any advise? Thanks, Frank
  6. Hello there! Ok, I'm very, very new to the Coco. They were never sold over here in Germany (AFAIK), and I got mine only recently from ebay.com. Here's my setup: - Coco 3 (stock - with a 512K RAM expansion and Joystick adapters on the way) - RE-FD502 disk controller connected to an HxC - Disk files converted from .dsk (renamed to .jvc) to .hfe So far so good. All 158K disk images seem to be working. BUT: It's the images bigger than 158K that give me a headache - remember: I'm a newbie! Case in question: "Alternate Reality - The City", which I downloaded from the TRS-80 Color Computer Archive. (GREAT site! ) The read-me says: This game must be started from a VDG screen/window. Since most advanced OS-9 users probably boot into an 80 column term, you must either have a vdg descriptor module in memory or know how to convert a standard window into a vdg screen. Conversion is simple, for example: xmode /w1 type=1 pag=16 shell i=/w1& and press CLEAR to access the new window NOTE: On NitrOS-9 type: xmode /w1 par=1 col=20 row=10 Of course I have to clue just what this means. I barely managed to get one of the many OS9 images to work with the HxC, but what now? All I get are various errors #s (216 and so on). It's probably a piece of cake for all you Coco lovers out there, but I'm really struggling with the various Operating Systems and disk formats. Maybe someone could give me some general help (remember, I'm using a HxC), and, especially, provide with some newbie-proof directions (or even .hfe images) of "Alternate Reality". Anyway, the Coco (3) seems to be a lovely machine. Thanks for all your help (hopefully), Frank
  7. Maybe that's why the original A8 Cobra is so huge/long... I seem to remember the booty just fits under its fin or tail (or whatever it is in heli lingo).
  8. I'm pretty sure the "Booty" is meant to be picked up, not shot at. (I have great memories playing this one with my father BITD - he still remembers the "xxxx miles cleared" melody, I just asked him today! )
  9. First of all, thanks a lot for tackling Super Cobra! It's one of the first games I've ever played on the A8 BITD, so it still holds a lot of nostalgia value for me. Having said this - the new version (only tried V1 so far) won't let me pick up the treasure ($) at the very end (PAL). Does this have anything to do with the new heli Player/Missile? Anyway, please keep up improving Super Cobra, your input is greatly appreciated!
  10. This is a good source (TOSEC-related) for all kinds of retro machines: https://archive.org/details/tosec
  11. Whatever happened to this site? No updates since 2006, now offline altogether. Shame, as this was quite well designed and a good read.
  12. Is there a manual for 3.0? Here it says: "not updated for version 3.0 - please wait for update"
  13. What's missing, though, is to go backwards within a directory, <SPACE> only produces the next batch of files, but you can't go back.
  14. That's it. Thanks a lot, Jay! Now, does anyone have a recommendation as to which firmware version to use? The latest 3.0 seems a bit buggy.
  15. Ok, me again. Hello. So I'd like to revert back from buggy 3.0 to 2.5, but no. It's either "card init error" or, using a different SD card - recognised with 3.0 - "firmware update not available" - though the sio2sd.bin (v2.5) is in the root directory. Oh dear, I regret the day I thought of "upgrading" my SIO2SD device might be a good idea. So, in a nutshell, how do I go back from 3.0 to 2.5? (Wait a minute! "Back from 3.0 to 2.5"... Now, this does ring a bell, doesn't it. History repeats itself... *lol*) UPDATE: Why, you little...?! You're not gonne believe this: suddenly my regular SD card was on the go again, even the downgrade to 2.5 worked - only to produce a permanent "card i/o error - format fatxx". Now, what does this mean? The card I've been using for years now had been formatted in FAT, no hassle for all those years. Now everything went haywire. Will give up now and put the Atari back on its shelf. For now.
×
×
  • Create New...