Jump to content

shalroth

Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

4 Neutral

About shalroth

  • Rank
    Space Invader
  • Birthday 10/18/1979

Profile Information

  • Gender
    Male
  • Location
    Leeds, UK
  • Interests
    Pushing vintage systems as far as possible and beyond. Proud owner of Atari 400, 800XL, 65XE, XEGS, STm, STE, STFM, Mega, Falcon030, six-switch VCS, 7800, Jaguar, Lynx and Lynx II.
  • Currently Playing
    Kyasurin, Portal 2 again, Doom 3 BFG Edition (stereoscopic), Mercenary, Paradroid

Recent Profile Visitors

2,247 profile views
  1. As promised, here are some photos of my 1MB 520STm with TOS 2.06. Sorry for size...
  2. Also, where you put it? Mechanically and electrically, I mean? It might have to piggy back on the 68000, ruling out concurrent use with an accelerator board or emulator board... The cartridge port is too slow (256KB/s) and only maps into 128KB of address space. The DMA port is an obvious alternative, (1.25MB/S) but there might be issues with other devices on the bus, and hanging it outside the case it's likely pick up electrical noise, which the DSP was never designed to encounter... the data would have to packetized as well, leading to inefficiencies and overheads... The simple answer is this: Atari already made an ST with a DSP chip... it's called the Falcon030! If adding a 56001 would require a 68030 as well, then you've got a Falcon without the lovely graphics, and no audio in without a sampler cartridge, which was one of the main reasons for using the DSP in the first place! Could the DSP perform the functions intended of the AMY chip? I'm not sure... AMY was an additive Sine-wave synthesizer, similar in operation to the decode stage of a vocoder in how it handled PCM playback. To simulate the AMY, you'd need wavetable memory to store the amplitude of the sine wave at various points in time. I've never coded for the 56001, so for now let's assume we can set aside 128K or so for our wavetables that the DSP can DMA to, so we can poke a value directly from the table into a 56001 register. Our code needs to read the next note value... maybe the DSP matrix could speed up the translation of the note value into the relevant amplitude from the wavetable. But AMY had 64 oscillators! Once we've set up our oscillators, the DSP transform matrix could be used to sum the sine waves, that's the sort of thing it's good at...but it's 24 clocks to fetch the note value, probably another 24+4 clocks to poke that into the DSP to look up the amplitude... and if we're doing that up to 64 times for each note... I don't think it would be feasible. DSPs are great for subtractive synthesis, it's a linear signal path. But additive synthesis involves multiple parallel operations, which I don't think they're great for.
  3. That's fair enough... I use it every time my Falcon boots... I did think initially that it was quite expensive just to get the Satandisk working but I've found it to be far, far more useful than just that. If you won't get the use out of it that's fine.
  4. I don't see why, the F030's 68030 sits on a 16-bit data bus, just like the 68000 in the ST...
  5. The PAK 68/3 accelerator for the ST had an optional FRAK board which could hold additional memory, but it probably uses the 68030's MMU and may appear as TT-RAM? I regularly emulate a TOS 2.06 STe with 14MB ST-RAM without (m)any issues. The CT60 accelerator for the F030 can add an additional 512MB apparently, but that has a 68060. I would never do that to a Falcon... it's cheating!
  6. Atari struggled to meet demand for the STe in late 1993 / early 1994 in the UK, according to ST Format magazine... I got mine in december '93, around the time the high-street retailers were deciding not to stock them any more. For a while, you could get a 520STfm Discovery Pack from Dixons for £79... and they were being snapped up as soon as they were put out on the shelves! I remember they had a stack of them in the middle of the shop floor one day, at least twenty units... and the next day they'd all gone!
  7. Thank you for this! I think I knew that byte swap only applied to volumes on IDE interfaces, but I forgot it as I'm only using IDE at the moment (I've tried half a dozen SCSI and SCSI II drives, with SCSI II and SCSI - SCSI II cables, and all sorts of termination options...but I just can't get them to mount. I've done it before, so I know I'm not too dumb to work it out, but for the time being it's beyond my abilities). My Falcon doesn't seem to be able to load hddriver.sys from a byte-swapped C: partition! I interpreted that as a failure of TOS 4.02, if the volume is byte-swapped, wouldn't it have trouble loading the driver because it can't read it at the XBIOS level? I'm very happy to be told how wrong I've got all this! I'm going to have to get a second CF-IDE adaptor and keep a byte-swapped CF card for transferring data to / from my Macintosh. I've seen your website a few times, and found the content very interesting. I'd love to know what other commercial TOS software is still in active development and support, but I'm not going to ask you for a list, I can probably find out myself I believe Papyrus is still available, but not for TOS; same with Calamus? (I have a licensed copy of Calamus SL and it's a fearsome application)
  8. In my ST days (by which I mean, when my ST was my primary computer) I didn't have any other ST-owning friends for about three years, and then he mainly had it for sequencing and had a mono monitor. I don't remember if he used to use it on a TV set as well, but the main data we exchanged were MIDI files and applications. I got my dodgy copy of Mag!x off him...but I don't think we exchanged menu disks (our school music teacher was quite relaxed about letting us have copies of Cubase Lite... it's ok now because it's freely available). Most of my friends had Amigas. Only one of them used it to it's maximum potential.
  9. If memory serves, it was usual for Atari to have machines hanging around for FIVE years before they sold! I got one of the 'unsold' Jaguars that Game found in a warehouse back in 2001 - from what I can tell it was manufactured in 1994, making it seven years sitting on a shelf!
  10. I used to do this too, in the dark days before I got my first hard disc. Calamus disk with fonts and a couple of accessories in A:, work disk in B:. Also, NVDI / MagiC (back when it was still called Mag!X) in A:, Application and work disk in B: (fortunately not many GDOS applications accessed the source disk too often, in my experience). Cubase disk in A:, work disk in B:... made for easier module loading... I may still be using some single-sided disks, but in a double-sided drive... and they're historical / vintage disks, so not my fault
  11. I wish I could find my SatanDisk. From what I've learned through replacing spinning rust with Compact Flash on my Falcon030, the key to easy Windows/Mac OS access is to use the 'swap byte order' option in HDDriver... the only problem is TOS can't boot from byte-order-swapped partitions, and I haven't found a way to mix and match (C: normal, D; E: and E: byte-swapped for example). You can boot off a floppy with HDDriver in the AUTO folder, or other mass storage device if you have one, and gain access to the byte-swapped volumes after boot. If you haven't already, please purchase HDDriver immediately. It's only EUR44 and it's worth every cent. It may also be the last piece of commercially available TOS software with active vendor support (my copy has a 2014 copyright date!) http://hddriver.seimet.de
  12. Partial credit! With TOS 2.05 or later, or MagiC (and presumably FreeMiNT) - from what I can dredge up - these boards supplement the MMU in the ST adding up to an extra 12MB. I found this on the Sound on Sound Atari pages: "Even though the ST's memory-management unit (MMU) can actually only handle 4Mb, the Magnum card supplements this, working in tandem with the ST's MMU to access the full 16Mb." Your Amiga analogy is bob-on. ST-RAM is like ChipRAM, in that the chipset and CPU need access to it because all the I/O is memory mapped there, the Video Shifter needs access to it to generate the display... so there's bus contention. TT-RAM is like FastRAM - the chipset doesn't need to access it so the CPU doesn't need to worry about being locked out of accessing it. So, I don't think games and TOS binaries will be able to see the extra memory, but after the installation of the driver to access the new MMU, I'm guessing it just gets mapped into the free memory pool - providing there's OS support.
  13. I have a PAL (UK) 520STm which my father upgraded to 1MB back in 1994/1995 (the STm is almost identical to the original 520ST, but it has an RF Modulator for television output). I don't remember which kit he used, but it was a commercial upgrade, not a hack. It must have been a Frontier / Marpet Xtra RAM, but not the SIMMs version (I had one of those too but never needed to use it). I can remember him complaining about the system being unstable, crashing more often than it did before the upgrade... he also installed a TOS switcher with 2.06 (software switched) which seemed to make it more stable, a few months before he abandoned TOS altogether and bought a Windoze system. I think that makes it somewhat unique - a 1MB 520STm with TOS 1.0 and 2.06! I haven't switched it on in about ten years, so I don't know if it's still in working order... it's possible some of the caps might have failed since then so it may need some help to get running again. I have a 14MB RAM upgrade to install in my Falcon030 later today (thank you Lynxman!) so while I'm at it, I'll try and remember to photograph the inside of the STm, and share my findings.
×
×
  • Create New...