Jump to content


New Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

8 Neutral

About Tekman

  • Rank
    Space Invader

Profile Information

  • Gender

Recent Profile Visitors

1,632 profile views
  1. It is confusing at first glance, but the board is 8Mb and not 8MB. 8Mb = 1MB.
  2. I would hate to see a hacked uncontrolled copy of ADEC out in the wild. I suggest you just update your ADE code like it suggests and also have the added benefit of all the new SD features and fixes from it. It’s surely easier than taking all the time to disassemble the ADEC code and figuring out how to remove it and still ultimately end up having a version not fully compatible with your ADEL. It's not hard to do at all once you get the programmer needed. The programmer is less than $8US and good to have on hand for any future updates. https://github.com/Kalidomra/AdamNet-Drive-Emulator/blob/master/ADE-Lite-Code-Update-Instructions.pdf https://www.pololu.com/product/3172
  3. It was released seven months ago. Official github page has update instructions. https://github.com/Kalidomra/AdamNet-Drive-Emulator
  4. The ADE developer doesn’t have an IDE setup to test with. It was found that when an IDE boot PROM is installed in slot 2 that it changed the boot timing of the overall system and was causing an issue with how the ADE is able to detect hard and soft resets and was causing the IDE to not work. That issue was believed to be resolved back in beta release v0.80 and had to be further tweaked in v0.91. If you’re running any version prior to v0.91, I suggest you update the code and see if it helps. If you're running the latest v0.91 code, try holding the DRIVE SELECT button to disable the auto boot disk feature to see if that helps. If this doesn’t do it, I suggest submitting an issue report on the official ADE Github project page. I'm just not sure how much troubleshooting can be done by the developer without a physical IDE setup. https://github.com/Kalidomra/AdamNet-Drive-Emulator/issues
  5. I’ll throw in my guess. The 74LS30 tells us it’s probably being specifically addressed to do a function, but without a processor it looks to be a basic function. It looks like the original design was ultimately focused on doing something with with the two GRN E? and E3 connection points off the relay output while E1, E5, and E7 look to be just ground connections. With it modified in its current state it looks like it isn’t doing anything except for simply shorting the two GRN E? and E3 connection points together and utilizing no control from the ADAM side circuitry. I have no idea what they were trying to do with it in its current modified state and can only assume it is incomplete. The color designations at each E connector makes me think it was using RJ11 connections and the hard pull-down 100 ohm resistor off one relay output side makes me thing it is a simple signal to indicate when testing or some function was completed? Maybe a simple LED on an indicator panel when testing was completed or an error condition occurred? I originally thought it must do more than just this but I just don’t see anything there that makes me think that. It appears to be simply triggering a latch circuit for the relay and nothing more. They needed these in some sort of numbers to justify a PCB run and I can only guess these were used in some sort of test environment.
  6. You’re talking about the Dallas DS1216E SmartWatch ROM. There was a guy on eBay that had a decent supply of NOS chips at one time but his supply has now dried up. If you can find a NOS one the battery is out of circuit until it’s power up for the first time. I'm certain all used ones have bad batteries by now. There’s info on the net that shows how to drill specific locations to sever old internal battery lines and how to wire an external battery to get them working again. You must get the E version of the DS1216 because it's specific for inserting in a ROM location. https://pdfserv.maximintegrated.com/en/ds/DS1216-DS1216H.pdf It’s a fun mod for about 5 minutes and then you’ll more than likely never use it again. It requires patching EOS every time you want to use it. I think only a couple applications natively support it and I think T-DOS might have a patch for it.
  7. No. You will need a center directory tape (SmartBASIC or similar) to format CD tapes and a right directory tape (Buck Rogers or similar) to format RD tapes.
  8. Here you go. C88 TECHNICAL SERVICE BULLETIN.pdf
  9. The second console I used for testing was a unit that needed the MIB238 C11 fix to work. After the C11 issue came to my attention, I pulled units out of my stash until I found a unit with the issue to troubleshoot with and now has become my second test console. Just to see, have you tried the alternate disk version from the archive as well as the ddp version? Between the official and unsorted images, the archive has five versions you can test with.
  10. Very strange. I just tried all three versions of Dragon’s Lair with three different MIB238 cards in two different consoles and all worked fine. It has to be your image or something with your console.
  11. I’m not aware of any titles that stop working when the MIB238 is installed. Dragon’s Lair works fine for me. Both the regular and alternate disk images as well as the ddp tape image all work fine for me. Perhaps you have a bad image?
  12. You can’t simply connect the modem as is to the terminal port and just change the MIB settings. The modem and terminal ports are wired differently for the specific task. Like NIAD said, would need an adapter to do it. Here are the pinouts for reference.
  13. Thanks! It's working great on the ADAM.
  14. Nice! Glad you're up and running.
  • Create New...