Jump to content


New Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

19 Good

About Doug_in_NC

  • Rank
    Star Raider

Profile Information

  • Location
    Charlotte. North Carolina, USA

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I didn't have a problem with my Ender 3 stock extruder - printed about 10 rolls of filament with it until the Bowden tube (the tube that feeds the filament into the head) loosened and I covered the inside of the head with PET fiber
  2. It wasn’t just the differences in disposable income, it was the prices charged. I always remember the comments in the computer press that the prices in USD for computer peripherals, memory etc was roughly 1 to 1 with prices in British Pounds when the actual exchange rate was 1.6 to one, ie a lot of peripherals, especially disk drives and memory was way more expensive in Europe. I still remember GBP80 or $135 for a 16k RAM expansion for a VIC 20.
  3. I have an 800XL with a Sophia Rev C (ie DVI output) card installed, that gives me a great picture on my old Dell 4:3 LCD monitor, but I'm having problems with the audio. I hooked up a composite + S-video audio cable to the conventional video out port and to a speaker with a built in amp, but all I get is a loud hum. The same with a cable that just has audio out. It isn't the cables or the speaker because I get decent sound (but meh video) with an unmodded 800XL with the same setup and either cable. Does anyone else had a similar problem and found a solution? I should note that the machine is also modded with a U1MB and I bought it in that condition so I have no proof that the audio issue is connected to the Sophia mod. I guess it could have a bad Pokey but that shouldn't give interference on the audio lines, right? I haven't tried taking the Sophia out yet, as I was hoping for some advice from someone who has seen this problem already before I start playing swap-a-chip.
  4. If you ever watch the Adrian's Digital Basement retro computer restoration YouTube channel, you would see he built what he calls a Commodore ZIFty Four by putting ZIF sockets in a machine that he uses for checking main chips (not glue logic or RAM) from faulty C64s. Anyone doing repairs on a regular basis would find an Atari board with space for Ziff sockets very useful. I can't see it being useful for many people, but leaving a little extra space around the main chips is one of those things that's good idea for those that need it and doesn't hurt anyone else.
  5. OK, that's reasonable. How about a really easy fix. On the Side 3 loader page on your website, it says "For proper Ultimate 1MB operation with SIDE3, please install the release candidate main BIOS and PBI BIOS for SIDE3:". How about adding something like "Please note this firmware is NOT backwards compatible with Side 2." or something similar.
  6. I think a lot of people would be happy with a U1MB bootup message providing a warning the firmware does not support the attached cartridge type if the "wrong" Side variant is in the cartridge slot. It would certainly have helped me 🙂
  7. Yes, I think the same way for the same reason - 32MB partitions at drives C and D with "removable" disks in A and B, even though the removable disks are much bigger than 32 MB 🙂
  8. Thanks. That makes sense. I will pull out my multimeter and soldering iron over the weekend and have a play. I have a stock machine too, so I can compare voltages etc between the two.
  9. On that case, mine is probably not that unusual. There's something unstable with my machine but I'm not sure what, though. I got the Fujinet, a SIO2SD and the Side2 working together for about 5 minutes this evening, rebooted and haven't managed to do so again
  10. _The Doctor_ I have the switch up. FlashJazzCat If I don't need the SIDE.SYS when the U1MB is running, why don't I see the CF Card drives when I don't install it manually? Is it not doing what I think it is? If I boot to command line prompt I can see the SDX is the version from the U1MB but I can't access the drives. I manually enter SIDE.SYS and then I can see them, but if I type CAR to go to the loader, I see xex files but not ATRs, which I should, right? I just remembered - I have a Side3 that is awaiting the new flash upgrade, so I have the version of U1MB firmware for the Side3 installed. Could that be the issue?
  11. I'm someone else having difficulty accessing the Side2 HDD from the U1MB too. As a newbie on the A8 I'm not entirely sure of what I am doing. I have the U1MB set up with a fresh installation of the firmware. Spartados X enabled, PBI Bios enabled, Hard drive enabled and boot drive = default. I have verified that the CONFIG.SYS on the CAR is exactly as in the Spartados X manual, ie it does not call out the SIDE.SYS driver, so I created an ATR that is mounted on a SIO2SD and contains 2 files - SIDE.SYS and a CONFIG.SYS that has the following in it: USE BANKED DEVICE SPARTA DEVICE SIO DEVICE ATARIDOS DEVICE ULTIME DEVICE JIFFY DEVICE RAMDISK DEVICE SIDE based on what someone else had in another thread. I have verified that on bootup the D1 is accessed before the prompt appears so it is loading something, but my CF card partitions don't appear. What have I missed? If I manually SIDE.SYS it loads the driver and I can access the drives without problem, so the problem is presumably that when CONFIG.SYS runs, it isn't looking for SIDE.SYS in the same directory as CONFIG.SYS is.
  12. Oh great. Any idea why it would be that low? The cartridge port reports a nice 5.01v and I have a modern PSU driving the 800XL it is on.
  13. The only thing I have found so far is that on my 800XL, Fujinet reports a low 4.7V on the SIO output, so maybe my PSU doesn't seem to have the grunt to get everything running happily. As soon as I saw that, I tried powering the FujuNet directly, which makes a huge difference to my WiFi connection, but doesn't help the compatibility with Spartados X. Neither the Side 2 Spartados (the latest firmware has Spartados X V4.49e) nor the one on my U1MB (again the latest, but this time V4.49) can access mounted Fujinet drives.
  14. David_P - did you discover anything? I'm having the same issue. HSIO set to 9, Side 2 installed, SDX running with drives mounted as C, D, E & F. FujuNet with drive mounted as A: and I get 138 error when I try to access the Fujinet drive. The Side 2 mounted drives function correctly. Basically it behaves as if the FujiNet isn't there.
  15. The cutters I have are fairly big, so I really don’t have space for them. I’m going to have another go desoldering, but if that doesn’t work I will pick up some finer wire cutters and try that.
  • Create New...