Jump to content

just.in.time

68000
  • Content Count

    1390
  • Joined

  • Last visited

1 Follower

About just.in.time

Recent Profile Visitors

1012 profile views
  1. just.in.time

    Micron Xceed docs on ebay

    Not sure if anyone is still following this thread. The pages here seem to match up to some of the pages visible in that eBay listing, as well as the Micron Xceed ROM.sit file containing a folder called Rob is Barts Friend, looks interesting but I haven't had a chance to actually look through the files. https://archive.org/details/MicronXCeedTechDocs/mode/2up Hope this is useful to someone, looks like it was uploaded almost a year ago (April 30, 2019).
  2. just.in.time

    Macintosh LC475 upgrades

    Unfortunately, it bombs out (type 10) while loading It made it just far enough to show off the splash screen, so definitely farther along than normal (an outright error about requiring a floating point unit). Definitely check it out. I grew up playing it on Windows computers. Had no idea it existed for Mac OS 7 through 9 until a couple years ago, or that there were two additional tables beyond the default Space Cadet table included with the Windows version. Would have been awesome to have had it back in the day, but better late than never. Aside from the FPU requirement, it's a fairly lean game in regards to system requirements.
  3. just.in.time

    Macintosh LC475 upgrades

    I haven’t! Never heard of it before, but I’ll give it a go tomorrow thank you!
  4. just.in.time

    Macintosh LC475 upgrades

    Definitely an edge case, but Space Cadet Pinball (aka Windows 95-XP pinball, Mac version) requires an FPU. (IIRC it requires a 33mhz 030 + fpu, any 040 + fpu, or any ppc). Was quite sad when it wouldn’t open on my PowerBook 540c. Maybe one day I’ll get a donor 550c full 040 cpu card. That aside, I’ve only heard of Sim City being sped up from an FPU (have not personally tried it). Logically, it makes sense that anything (games, audio, apps, compression/decompression, etc???) working with Float data types would benefit from an FPU, but the degree to which it improves real world experience I’m not sure. All that said, when I swapped a full 68040 into my LC 575 board it ran toasty. Definitely recommend a heatsink. (33-25)/25=0.32... that’s a 32% increase in clock rate. FPU bound tasks aside (pretending both are 68LC040 processors), I’d be surprised if there wasn’t a perceivable difference in overall responsiveness during a side-by-side test. Adding in the FPU on the 33mhz cpu only increases that performance gap, wherever the FPU may be helpful. That said, I’ve never compared a 25mhz and 33mhz 040 side by side. Please share the results of your experiment. It would be cool to know if you felt the extra clock speed was significantly noticeable. Also, if you have the ability to try decompressing the same large-ish StuffIt file on both systems with a stopwatch please do. I’d be curious to see the time difference, if any.
  5. just.in.time

    Marginal Power Supplies -- What are the symptoms?

    Despite passing hardware diagnostics, I wouldn’t rule out faulty RAM too soon. If you have enough (such as 8 sticks), try running with just 4 sticks. If one batch happens to be 256k then you will be knocked back to system 6 with that 1MB of RAM but just for testing purposes. Try different configurations for a couple days. That said, it could very well be a voltage dip causing your issues. The external floppy drive port is the easiest place to measure voltages. Get a voltmeter and rig it up to the appropriate pins (pin out available on google) to measure each of 12v and 5v (iirc I think you can see both + and - there, so 4 measurements). Careful to not cause a short! That would make for a bad day. Once you have a safe and reliable connection measuring voltage, make sure it is within a good tolerance of range (again, been 3 years since I did mine but +/- 0.05 v is okay I believe double check to be sure). While measuring, turn the brightness up, pop in a floppy, use the keyboard, etc. to help put more electrical load on the system. Continue to monitor voltage and verify it doesn’t dip significantly while under load. Last but not least, that board washing. If the dishwasher has worked for you in the past then do what you have had success with. My personal method is to wet board with distilled water, spray down with original Simple Green, and use a soft bristle toothbrush to gently scrub the board. Then, I rinse all Simple Green off with distilled water. Finally, I rinse with rubbing alcohol to displace water. Compressed air can to remove any remaining liquid. I follow this up with a drying session of 1 hour to make sure everything is really dry. I avoid the dishwasher because of the high mineral content of the tap water in my city.
  6. just.in.time

    SCSI2SD Issues

    If you have others working just fine, I’d try taking one of their SD cards, put it in the problematic unit, and see if that rules out the issue. If yes, formatting issue. If issue persists, firmware configuration issue on the SCSI2SD itself. If that’s the case, I’d download the firmware from the web, reflash it, then make sure config matches a known good unit.
  7. just.in.time

    SCSI2SD Issues

    I generally just stick to 1.99gb partitions (except for my pm6100 that I let utilize the whole sd card), just to be safe.
  8. just.in.time

    SCSI2SD Issues

    @techknight if I’m not mistaken (though I may be), the SCSI2SD v5.x boards have on board termination and I want to say it is enabled out of the box (physically on older red boards, via firmware on newer green boards) I’ve had great luck setting up ~5 of these (SE/30, SE FDHD, CC, LC520/50, and a PM6100), all bus powered with only one of which I tried to play with the config settings on. Usually I just pop in a new SD card, plug into the Mac, and use Lido to partition the SD into ~2gb partitions (except the pm6100, let it have all the space on OS 9.1). I give 4 partitions and leave the rest blank. I imagine the starting format of the SD card is fat/exfat or whatever would be PC compatible. Lido reformats it to Mac HFS. On the pm6100 after Lido I think I reformatted from finder to HFS+ prior to OS install iirc. But it’s been about a year since I set one up, maybe newer firmware has a bug or something.
  9. just.in.time

    Studio Display m7613

    Thank you @Juror22 and @OleLila for the advice. I usually try to avoid taking things apart until I have all the replacement pieces on hand so I can complete the project in one go, but it’s looking like that won’t be possible in this case. I’ll probably open it up next weekend and see if I can’t locate the number. The real shame is that, aside from the gouge marks, the panel is impressively bright. Oh well.
  10. just.in.time

    Studio Display m7613

    Bump, anyone?
  11. just.in.time

    Studio Display m7613

    Hi all, I bought a 15” Apple Studio Display, model M7613. It’s one of the early flat panel displays that matches the early PowerMac G4 plastics (think 350mhz G4, AGP graphics model, and maybe the digital audio model?), with a DVI and USB connector, and 1024*768 resolution. At any rate, the LCD panel has a few gouges in it. Does anyone know the part number for the LCD panel? I’d like to try to replace it to make it like new again.
  12. just.in.time

    Fitting a SCSI2SD in a 68k Mac

    +1 for Lido
  13. just.in.time

    Building a Spotify player for my Mac SE/30

    @ants Thank you for all your help on this. Do you remember which retailer you got your 16M version at? Both Amazon and Newegg only carry the 16M version with internal antennas.
  14. just.in.time

    Building a Spotify player for my Mac SE/30

    @ants I was actually just typing up an update when I saw your reply. I found that same OpenWRT page too (https://openwrt.org/unsupported/nand_flash). No worries, now we know so we can document this so that anyone else that attempts this setup knows which version to purchase. Did some quick research, and it looks like the GL-AR300M NAND memory portion isn't supported for the installation of OpenWRT. The NAND version does supposedly also have some NOR memory on board, but getting the ar300m/-ext to check there for booting purposes is an exercise (after enough failed boot attempts from nand memory it might attempt booting from nor memory for one boot cycle). And even then, it's unclear if the onboard software will allow the "nor" version of OpenWRT 18.06.x to be applied. So based on all this, the "safe" list of GL-AR300M versions are: GL-AR300M16 (internal antennas, 16m NOR memory only) GL-AR300M16-Ext (external antennas, 16m NOR memory only) --The version you (@ants) are using And the two that aren't supported at this point in time (at least, not without some sort of workaround): GL-AR300M (internal antennas, 128m NAND memory and maybe 16m NOR memory as fallback) GL-AR300M-Ext (external antennas, 128m NAND memory and maybe 16m NOR memory as fallback) The product info above I found at https://www.gl-inet.com/products/gl-ar300m/
  15. just.in.time

    Building a Spotify player for my Mac SE/30

    @ants Gave that image a try, but still the same error. Basic Interface (non-advanced settings): Listed at bottom of screen: Model ar300m NAND (so I think you are right on the nand version, I'll give a few more nand options a try) Luci Interface: Here are some details from the system: Model: GL-AR300M Firmware: LEDE Reboot 17.01.4 r3560-79f57e422d / LuCI lede-17.01 branch (git-17.290.79498-d3f0685) System/Software/Configuration/Distribution Feeds: src/gz packages http://www.gl-inet.com/lede/2.27/ar71xx/nand (so again I think you are right about the nand memory) Details from System Log: Mon Apr 9 21:17:36 2018 kern.info kernel: [ 0.000000] CPU0 revision is: 00019374 (MIPS 24Kc) Mon Apr 9 21:17:36 2018 kern.info kernel: [ 0.000000] SoC: Qualcomm Atheros QCA9533 ver 2 rev 0 Mon Apr 9 21:17:36 2018 kern.info kernel: [ 0.117209] MIPS: machine is GL-AR300M Mon Apr 9 21:17:36 2018 kern.info kernel: [ 0.834536] nand: device found, Manufacturer ID: 0xc8, Chip ID: 0xb1 Mon Apr 9 21:17:36 2018 kern.info kernel: [ 0.841168] nand: Giga Device GD5F1GQ4U 1G 3.3V 8-bit Mon Apr 9 21:17:36 2018 kern.info kernel: [ 0.846381] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128 I'll keep digging around in that NAND directory at openwrt's site, maybe one of them will do the trick. Thank you for the tip on memory type differences.
×