Jump to content

Nezgar

+AtariAge Subscriber
  • Content Count

    3,181
  • Joined

  • Last visited

Community Reputation

2,458 Excellent

About Nezgar

  • Rank
    River Patroller

Contact / Social Media

Profile Information

  • Gender
    Male
  • Location
    Saskatchewan Canada

Recent Profile Visitors

7,110 profile views
  1. The clicks are at about 200ms intervals when I tapped it out in a tempo finder, so my guess is it's related to the wifi beacon frames transmitted from your AP, which are often in multiples of 100ms, plus a DTIM multiple of 2 as a common default. The DTIM interval allows low-power wifi radios to "sleep" and will "wake up" every 2 beacons for the "Delivery Traffic Indication Message" to see if any traffic is queud for the device.. The random other intermittent clicks may be from other traffic on your wifi network, or broadcasts. How far away is your AP from the Fujinet? Is the audio noise present on the audio-out of the atari, when not running through the monitor? If it is just the DTIM 'wakeup' of the FujiNet, the interference would be from the processor in the FujiNet itself...
  2. I guess it would make sense for a DOS loader, if it loads below that, and then is free for re-use once control is transferred...
  3. Maybe it would work if the file is placed on a SpartaDOS disk and then set with the "BOOT" command? From the SDCS documentation: The DOS loader on the first three sectors of each SpartaDOS 2.x formatted diskette, can load and run files in the same manner as a command file. Normally DOS is loaded, but actually anything could be loaded as long as it avoids the loader memory ($2E00-$3180). <snip> Example BOOT STAR.BIN When this diskette is booted, it will immediately try to load and run the file STAR.BIN. I've made "quick boot" disks for some utilities this way as long as they're single-segment loaders.. Some games, RAM testers, UAV colour/artifact test utility etc worked...
  4. The thing with the Archiver -- unlike most other "enhanced" drives -- is that it's extended commands were not available by default until a special "open code" was sent to the drive, or it was turned on with a special disk in the drive, so it was pretty immune to detection. The code was a 2-byte code unique to each drive, so it would take up to 65,536 attempts to even attempt brute forcing it by software. The happy for instance you had to explicitly set it to "unhappy" to disable the extended commands and track buffering. Regardless, always a good idea to write protect those disks hehe
  5. Your original would have been write protected. A.E. came out in '82 and 1050 hadnt been released yet. I dont think the 810 versions of the happy had a software controllable write protect.
  6. As an early copy protection mechanism, IIRC Brøderbund's "A.E." checks if your disk drive responded to Happy commands, and if so issue a format command and show "Gotcha!" on the screen. In theory with the controller add-on, it could have also disengaged a write protect by software control if you hadn't disabled that function...
  7. Maybe a replica of the of a Best Electronics PCB: "Best Upgraded 4th Gen. Gold CX40 Internal PCB CO121110G $9.95 each (Min. 2 Qty per order)" Scroll waaaaaay down: http://www.best-electronics-ca.com/joystick.htm
  8. The thin wires would definitely be a factor, but I've seen only dropping to about 4.5V... anyhow, the cord on the ingot PSU is 18AWG I think. Much thicker.
  9. I would keep the C64 PSU as far away from your atari as possible... even with an adapter... Use your efforts to splice a DIN connector onto a USB cable and use a 2.0+amp phone charger instead. This will be much more useful. Edit: yes I agree with @_The Doctor__ - use the cutoff DIN pigtail from the ingot to attach to a USB connector
  10. I fully agree regarding the benefits of the main memory mirroring... Just refreshing my memory here... (there's a pun...) But reviewing the A8FAQ the "original" Peterson type upgrade description notes that main memory was protected from banking, and something about bit 5 being "inverted" compared to RAMBO type upgrades (what does that mean?), and later mods supplied after "Rambo" type upgrades gained popularity to allow banked access to main memory and ANTIC access to banked memory switched to CPU calling the "256KXLE" Methinks there may be a connection here....
  11. The upgraded power board uses a 7805/7812, the original uses a power transistor (Q113) and a voltage regulator (A108) - not sure at the moment. The 7805/7812 in the later rev power board are in the places of J104 and J105 on this board... The Rev 1 service manual would be what applies to @80sAtariboy's drive. ie (Page 6-13 and Appendix D for the rear board) http://www.atarimania.com/documents/Atari_810_Disk_Drive_Field_Service_Manual_Rev_1.pdf
  12. Well, that's definitely the "earliest" 810.... It's missing all of the enhancements Atari incrementally released for the 810 during it's production. It has the old power board, no top analog board, and probably no data separator daughterboard and a Rev B ROM... From my experience even in a "working" drive without those upgrades it will be temperamental.. The slightest nudge of the RPM trimpot on the power board will throw off the speed by +/- 10RPM... And the power board is insufficient to power up if you add a data separator to the side-board too.. Anyhow - you may have your work cut out if you don't have another 810 to swap parts from. Best electronics sells all the components for the "Grass valley upgrade kit" - but you could probably buy a few used 810's for that price... With the drive off, can you manually slide the head transport forward back, or is it seized? The 810 has no track 0 sensor.... But moving the head to the middle and powering up might be a good test... Normally if an 810 has issues reading, the firmware will smash the head backwards and make a grinding like an Apple Disk II to try to realign the head before retrying.... if you always power off the 810 after it has spun down and returned to track 0, it should "normally" never do this.... But it got quite a reputation on copy protected disks with intentional bad sectors invoking that behaviour, etc. There were ads for patched ROM's that would minimize it... ie CSS's "Silencer"...
  13. Hmm.... it's normal to boot to self-test since the BASIC ROM is not present (But it should still boot a disk if a drive is attached), but not normal to go immediately to the memory test. Does the memory test actually indicate any red blocks? (should only show 40 blocks though, not 48 in this mode) Also compare with option held down - which should disable the BASIC ROM (or in this case, the 810 ROM) I'll try to give this myself and refresh my memory what's supposed to happen and I'm actually giving you good advice...
  14. Hello.

     

    I have noticed you have been posting about roms for the Atari xegs.

    I am in need of a rom and have a programmer and a bunch of 27c256 eproms.

    All I am needing is the bin file.

    Would this be something you could supply?

     

    Thanks.

    Gord

    1. Show previous comments  7 more
    2. GoldLeader

      GoldLeader

      and they're crunchy!

    3. x=usr(1536)

      x=usr(1536)

      They remind me of certain insects.

       

       

    4. Nezgar

      Nezgar

      This inspired my new profile wallpaper :D

      atarimallow3.jpg

×
×
  • Create New...