Jump to content

Frobozz

6502
  • Content Count

    37
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. I suppose that sentence would have been better without the "good". A debugger, period, is worth a bit. And yeah, Eclipse is a bit of an 'acquired taste', shall we say. I actually have a pretty good feeling about visual studio code (I just wish I could make it work for Retro68). back in the day, I didn't really program for either platform. I had both, used both regularly, but wasn't doing any real dev on them. A few years ago I got the bug and started doing C-128, Amiga, and Mac 68K programming for fun. So no baggage. It has been REALLY interesting having a foot in each community a
  2. nice! and can I say that I love the Big Sur desktop background on the olde Macs?
  3. That's a legit question. For me, not speaking for anyone else, part of the answer is usually "because I can". So, partly about the journey, if you will. But on a practical level, here are some of the reasons I prefer cross-compiling to native-on-retro-hardware (even if virtual): version control. This is reason 1, 2, and 3. Maybe something is possible with Basilisk, since it can mount a shared Mac folder, but I haven't used Basilisk in 15 years or so, so I'll have to play around with that idea. Files with resource forks are going to be a challenge of course. (mini vMac doe
  4. Well, since I made that comment about BBEdit, I thought I might as well add that configuration as well. It was painless, and I think I like it better at this point. I am going to miss Eclipse catching dumb typos and mistakes for me before I even build, but there's a lot to be said for a fast UI and great search abilities too. Here's a little write up of how I configured BBEdit to work with Retro68. Setting up Retro68 Retro68 setup is beyond the scope of this post, but after you get it built, you need to configure the LaunchAPPL tool to point to your favorite simu
  5. I'm trying to get a good cross-compile environment set up to write 68K Mac apps from my modern Mac (OS: Big Sur). I've tried 3 IDEs so far, with mixed, but distinct results. Curious about others using Retro68, and their experiences. Hopefully this will be helpful to me, and also anyone coming along with the same questions. Retro68: https://github.com/autc04/Retro68 CodeLite I hadn't used CodeLite before. It's a cross-platform IDE with C/C++ support. It's fairly zippy, not Java, but doesn't use native OS X controls, so some things like cut/paste need right-c
  6. Very interesting. I bet with some tuning you could get the contents display to be even more friendly to classic Macs. maybe options to remove all images, convert unicode curly quotes, bullets, etc, to MacRoman code points, etc. Not all sites will be great of course, but just being able to view HTTPS sites on say an SE/30 or Plus would be pretty amazing. Just heard of MacIPgw for the first time... You have a VM running on that with the image from here (https://www.macip.net/macipgg-vm-3-0/)?
  7. There's a Total Systems 68030 accelerator for the Plus up right now on eBay: https://www.ebay.com/itm/Mac-Plus-Logic-Board-w-Quesse-68030-Accelerator-incl-68882/333855393411 Doesn't say how much RAM is installed, and it looks like the Mercury version, which I believe is only 16mhz. is it like fantastically hard work to reverse engineer/copy one of these? I've seen the 040 reproduction for the SE (if I remember right) here. Hardware is a mystery to me. If I touch it, I'm pretty much guaranteed the magic will leak out.
  8. Yeah, the resource fork is going to be fun. I would also like to build in an option to translate the charset when it made sense. I haven't thought this out in any detail, but maybe something like this: On 68K Mac side: raw folder: contains raw Mac apps, text files, etc. sync folder: contains processed files. If app: hqx applied if .txt: charset, line endings translated (e.g.) On Modern Mac/pc side: raw folder: contains text files with modern Mac/pc line endings/etc. (obviously, I don't mean U
  9. ha, I don't actually have an ST either, but I like the idea of it being a more general retrotool (set). I have an Asante SCSI adapter I've used in the past (looks to be same idea as the DayPort SCSI/Link?), and an old ethernet hub that it could access, but I don't have a good way to connect that to my current Mac setup (router now on other side of the house). What are peopled doing who want/need a wireless solution? Hook the SCSI adapter into a wireless bridge? Does that tend to work? Writing a SCSI to ethernet adapter for the Amiga sounds pretty hairy to me. I can im
  10. Let me try to describe it a bit better: User wants to have a common folder synced between TWO computers (this wouldn't work well for more than 2). Any combination of 2 below: Modern Mac (or PC, or Linux) 68K Mac (or probably more accurately: System 6.x ~ 9.0 Mac). I don't know enough about systems < 6, and 512K Macs to say if it would be. possible to get a version running on a 512K Mac) Amiga Atari ST (or any classic computer where someone wants to work on a port, and serial is available) User does not have SLIP
  11. Can you describe a bit more how you use FreeFileSync with your classic Macs? Does it require a TCP/IP stack running on the old Macs?
  12. Ah... AppleTalk Remote Access. I vaguely remember that. manual for 3.0: https://vintageapple.org/macbooks/pdf/AppleTalk_Remote_Access_3.0_Users_Manual_199x.pdf Links to what I think are older versions: https://macgui.com/downloads/?cat_id=234 ------- Apple Remote Access 3.0 requires the following hardware and software: m a computer with a 68030, 68040, or PowerPCTM microprocessor m Mac OS version 7.1 through 7.1.2 or Mac OS version 7.5.3 or later (not earlier versions of system 7.5) m at lea
  13. I'd like to have a watched directory on my modern Mac, and on my Mac Plus, which syncs itself with very little effort from me. (Given non-multitasking nature of the Plus/OS 6, I think user will have to take the action of starting the sync tool and letting it run; not sure how well it will perform when running in the background on System 6). I have my Plus connected to my Big Sur Mac with a Keyspan adapter, using Serial (the app) in place of working serial drivers. I do some Modem transfers that way. I also have a SCSI2SD, which is pretty awesome, but not actually all that easy to transfer file
  14. For why more speed on B/W Macs, I would say: development (THINK C, etc.) general system snappiness. Try using miniVmac at like 4x speed, then a mac 128/512/plus/classic for general tasks. You'll notice a big usability difference. (not speed, but memory): having more than 4MB would be nice. Not 64 GB, but 8 or 16 would be quite nice. For 68000 overclocked vs 68030, I would maybe suggest (not an expert here): Apparently a bit more stable (at least compared to wicher). I haven't experienced any stability on my 50mhz 68030. having FPU is nice for l
×
×
  • Create New...