Jump to content

Ed in SoDak

Members
  • Content Count

    695
  • Joined

  • Last visited

Community Reputation

400 Excellent

About Ed in SoDak

  • Rank
    Dragonstomper
  • Birthday 03/24/1955

Contact / Social Media

Profile Information

  • Gender
    Male
  • Location
    Black Hills of South Dakota

Recent Profile Visitors

4,967 profile views
  1. Ok, that's the reason it won't work for all cases by just renaming it. I don't use the custom menu options myself in emulation. On real disks I did BITD. As long as you didn't customize it, you'd be fine naming it UTIL1 I think.
  2. There is a notch on the top right corner of a floppy. If that's covered, the disk is write-protected. That, or the write-protect sensor in the drive is faulty. Next, if that seems to be ok, is there room on the disk for your additional file(s)?
  3. Can't you just rename BOOT to UTIL1 instead of editing the EA .bin? Or have a second copy of BOOT, rename one and keep the other copy with original name. I used that trick with Funnelweb.
  4. Yes, they do have voltage on the probes in the resistance ranges. Polarity isn't always red for +, black for -. I've used another meter to check the probes on my subject multimeter/DMM. There are little multitesters these days that will read an inserted chip and give you the stats for it. Might not cover all the chips you need to test though... -Ed
  5. 5.25 disks are probably old, just like the 99/4A. Some HD floppies won't work as well as the DSDD types. Not sure what you're using, but another thing to look at while trying to chase it down. Were these disks already initialized with files on them? How many have you tried? Always possible something got scrambled on the disk when a write went south. Can you reformat one to try it fresh? You need a disk manager cart or program on disk. I had a problem with the LED that detects if the disk's write-protect notch is covered. Wasn't dirt, the LED itself went bad. Another guess that also gave me trouble if I forgot about it, if the drives are uncovered and the room lights are bright, that can mess with the sensors too. Toss a cardboard cover over it or try with the lights down. If the drives are in enclosures, that's probably not it. Since you're testing, I figured it's possible you have it laying out exposed to room lights. Could try very lightly lubing the rails the head moves on. Usually when I have a drive problem, I just pull out another one from my TI hardware stash and carry on. I have a few I swapped out that need looked at now. Running low on spares... -Ed
  6. I host a few pages with old metal detector manuals and info. I get a few genuine detector-related emails in foreign languages. Most have been for things I don't provide like unobtanium schematics and obsolete parts or detectors for sale. I've used online translators to reply, but gave up that plan when the Arabic ones showed up. Almost never hear back or get a thanks anyway.
  7. A TI spam, you say? It's not like anyone would ever guess you were into the TI.
  8. Tsk. Where's your spirit of adventure? Getting old programs to work by hook or crook is good for the soul!
  9. +1000 for Tursi and Classic99! I have a USB Xbox controller which the XP laptop recognized. It works in Classic99 for the carts I tried, but wasn't supported in SXB. Still not bad and I was able to use what I already had laying around. I should pop for one of the adaptors and up my game.
  10. The link on archive.org also has the full text. It's not without some OCR errors but with referring to the PDF, these could be corrected. Probably none of the listings are too long to fix up and use. Copy/paste into notepad, edit, then paste the corrected listing into Classic99.
  11. Yabbut, who's gonna go into a shop just to look at 100 zener diodes?
  12. I aimed my pointy finger at your monitor, but I gave your modulator a pass. When that turned out to be the problem, it made me recall the time I had a modulator go bad. In my case, I just swapped in one of several from my stash and I was off to the races again!
  13. The sticks are way too stiff, besides the weak membrane contact design. Maybe if they had a comfortable knob on the end and somehow made easier to move but still self-centering, then install microswitches to get rid of the membrane. Cords are stiff as well, and the controllers are so light, the cord alone will drag them around and they won't stay put. "Pain Sticks" is a good moniker for 'em! My "cure" was to chop the cords off near the controller and splice them onto two non-matching but decent Atari-style sticks. I left those cords long as well, cut off close to the plugs. No adapters needed, but they're no longer Atari-compatible. Bonus was double-length cords!
  14. Glad you nailed the culprit. Much easier fix than digging into the console!
  15. If your XB program has the space, you can add some DOS-like functions with CALL SUB. My thoughts when I was programming a lot was why exit my program just to do some simple file-related task. I took my favorite XB LOAD program and tuned it into a SUB. The one I chose has a disk directory with options to delete a file, load a program or view/print a text-type file. I added CALL CLEAR :: CALL DIR(KOR): as a menu option which then ran the SUBprogram XB LOAD. My SXB cart has a CALL CAT as a command, but that doesn't support file viewing. I used DIR for my subprogram name to avoid conflicts with CAT. KOR is the variable name I used for the character number of the last key pressed to avoid conflict with the variable K that's typically used in many XB programs. I have another small program called FILEREAD that could be added in the same way and I used that in another program I wrote along with XB LOAD. For the example I show below, the only listing I happen to have handy is just a disk catalog, but the same process would work to add any small XB utility program you like to any other XB program. As long as there's enough memory for it to fit. To use it as a CALL SUB, I just renumbered the original XB utility to put it at the end of the main program and changed anything like variables, screen colors, etc. that might interfere with the main program. Save your add-on as a MERGE file and insert it into whatever program you like, space permitting. The just add the menu choice and the CALL DIR(KOR) This all might be getting away from designing the Ultimate XB, but it describes a way to add a little extra power to our old and comfortable version of it. The downside is it's only useful in a running program and it robs some memory space. Usually there's not that many programs out there which use ALL of XB's memory space. That's why I figured why not add a little icing to my own programs and use some of that idle RAM.
×
×
  • Create New...