Jump to content

ACML

Members
  • Posts

    1,463
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    USA

Recent Profile Visitors

12,389 profile views

ACML's Achievements

Stargunner

Stargunner (7/9)

809

Reputation

  1. I have owned both form factors and without a doubt, to me, the new Lotharek Fujinet Pro (v1.7) is an outstanding choice. It's built very solid. It does require a SIO cable, but those are like $15-20. The issue I had with the original form factor was that it was a very tight fit in the SIO port, and my fear is that the 3D printed SIO connections could be more prone to failure because of the direct stresses on the PCB they are attached to. The build quality of the Lotharek Fujinet Pro is much better than the original form factor. Other comment: I see a lot of 3rd party SIO cables that don't include all 13 lines. What's up with that. I know some devices only need, say five of the 13 lines, but if the cable is in a pass-thru configuration, it won't pass the other 8 signals. For that reason, I opted to use an OEM SIO cable to ensure all 13 pins would be available for any downstream devices in a pass-thru configuration.
  2. I've upgraded a lot of 1200XL motherboards and I've noticed that the older REV 13 boards have milder jail bars than the newer REV A 1200XL motherboards. Don't know why, but I'm noticing a trend. The jail bars already exist in the stock LUMA signal going to the monitor jack. Plug a stock 1200XL into the s-video of your LCD/LED flat screen and you'll see jail bars in the B&W s-video (i.e. no CHROMA connected on the jack). Point being that the jail bars effect is already there before modifications.
  3. I've noticed that a stock 1200XL has jail bars and it's there in the LUMA signal. That means the stock video circuit that does not have CHROMA connected to the monitor jack already has the jail bar effect in the B&W LUMA signal going to the monitor jack, so I don't think the ClearPic2002 mod introduced the jail bars as they were already there.
  4. Of all the 1200XL keyboards I've seen, they all have a glossy dark key. The 800 (beige), had flat (Hi-Tek and Stackpole) as well as glossy (Mitsumi) keys. Like kheller2 stated, the letters were either really bright white or just a shade off. Any abrasive on plastic would likely dullen or damage the lettering.
  5. Xuel, That did the trick. Works great now on a SDRIVE loader. Thank you very much, again!
  6. The SDRIVE has no problem loading previous XEX versions of Joust, so the issue is with this XEX file, not the SDRIVE.
  7. The SDRIVE loader has been around awhile and is pretty robust, so I feel there has to be something different about this XEX.
  8. This version still won't load and execute with the SDRIVE loader for some reason. When the load finishes, you just get a silent black screen.
  9. I have no idea what the screen clitch was, but the main issue fixed was that the proper space was added between the left score and the lives remaining symbols. It's a small thing, but someone fixed it. Xuel has cracked many games to be compatible with XL OS and is very talented in 6502 coding. He has fixed many game issues in the past.
  10. Any idea why this won't load with SDRIVE? It works fine with SIO2SD and Fujinet, but the XEX on SDRIVE will not execute. It loads, but goes to black screen and never starts.
  11. Is the pin circled supposed to be connected to that thick trace or is that a short?
  12. By looking at the PCB traces, I think your BREAK key might also be an issue. The BREAK, CTRL and SHFT keys have a common trace. You can test the CTRL and SHFT keys using the HELP keyboard function, but not BREAK. To test BREAK, pop in a BASIC cartridge and at the READY prompt, press BREAK, the cursor should drop down one line. If it doesn't respond, it too is affected. If that is the case, you either have a broken trace in the mylar as Beeblebrox mentions above or if that one trace corresponds to one of the nine fingers that meet at the PCB, you may have not built up the carbon trace to the same height as the other 8 fingers and that no is not making contact. If BREAK does not work, the issue is on the green PCB side and likely not the mylar side.
  13. Figured it out. When you press CTRL-W to save config, you have to type "L" for long names and then "Y" for yes. SDrive_manual.pdf
  14. I have tried hitting CTRL-L to get the long name and it works, but then I hit CTRL-W to write config and it appears to do something. Then when I reboot, is defaults back to 8.3 short names. Also, has SDRIVE always had joystick navigation?
  15. I keep my shields on. Not to hijack the thread, but 64K for me is really enough. If I want to play 64K or 128K XE carts, I use the UNO cart which works great on stock 64K machines. Even larger CAR or ROM images can use the Ultimate cart on a 64K machine. Not planning to use word processors or spreadsheets bigger than 64K limits anymore. Also, some 256K DRAMs discharge slowly and you have to leave the power off for 3-5 seconds to ensure a cold start.
×
×
  • Create New...