Jump to content


  • Content Count

  • Joined

  • Last visited


Profile Information

  • Gender
    Not Telling
  • Location
    Melbourne, Australia

Recent Profile Visitors

1062 profile views
  1. ants

    System 7 & Philips Hue Lightbulbs

    That is awesome!! Well done!!!
  2. ants

    Fun with colour on my SE/30

    Sure - PM me and we can sort something out.
  3. ants

    Fun with colour on my SE/30

    Hi all, thanks for your ongoing interest - however, I've decided not to continue with this project. As cool as it was to see a colour screen in an SE/30 - for me personally I feel the original B&W CRT is a big part of what makes these old machines so special. Staring at an LCD in a SE/30 just felt wrong, which is why I haven't been motivated to keep going with it. I also own a Mac Colour Classic - it's Trinitron CRT is wonderful and this machine was always made for colour.
  4. Thanks @Crutch and great work on releasing your screensaver. I'm using Retro68 which is a gcc cross compiler on my Windows 10 laptop. It's using C++ 11, which I believe the full library is over 10mb - so I think it's already only including the bits it needs. It just shows how software gets more bloated as the years go by! I've got some ideas on how to reduce the file size, but failing that I'll definitely look into Codewarrior.
  5. The simplest thing would be to rewrite it in C - that'd probably get it down to about 200k...
  6. That's the problem. The extension itself is over 2mb in size, and it's memory requirement is set to 4mb. On a SE/30 with 128mb of RAM that's of course not an issue, but I didn't realise the SE's maximum memory was so low! The reason the extension is so big is due to a combination of factors: It's written in C++. The C++ library is almost 1mb in size. I could rewrite it in C, but that's a big job and I'm not much of a C programmer. The extension relies on a number of other libraries. The biggest on is iconv at almost 1mb which is used to convert UTF-8 text to MacRoman - however this is only required if you plan to use the Spotify app I wrote. Attached is a version of MacWifi with a reduced memory requirement of 1.5mb. I've removed the iconv library from this build, but I've kept the logging code in for now. Give it a go, but unfortunately it's not going to leave you with much free RAM for other applications. MacWifi.APPL.sit
  7. How much RAM is in your SE?
  8. @Michael_b Attached is a version of the extension with some logging added. Before installing, please rename your primary disk to "Mac HD (68K)" (without the quotes). Solely because I was too lazy to write the code to find the primary drive... Then after rebooting, wait a few minutes and you should see wifi.txt in the root of Mac HD (68K). Please post the contents of this file. If there's no file we're really in trouble! MacWifi.APPL.sit
  9. eBay. This is the exact one I bought, but there might be cheaper sellers around: https://www.ebay.com.au/itm/GL-AR300M16-Ext-mini-router-300Mbps-WiFi-OpenWrt-Repeater-OpenVPN/223044703527
  10. @just.in.time thanks for the information. To make myself feel a little better, I've updated the Readme on the GitHub page with this information: https://github.com/antscode/MacWifi
  11. @Michael_b @10001001sos I finally had some spare time and I believe I've figured out the issue with System 7. The issue was not MacTCP as I originally thought, but simply that you need to install the Thread Manager extension. I had previously only tested the extension on System 7.5, which has Thread Manager included - but it's not included with earlier OSes. Here's the MacWifi extension running on System 7.1: I've updated the Readme on the MacWifi GitHub page to include information about Thread Manager: https://github.com/antscode/MacWifi
  12. @just.in.time sorry, if I had of known the packages were different I would have made this clear on my GitHub readme I also found this on the OpenWRT site: https://openwrt.org/unsupported/nand_flash Note the table at the bottom: It says must be forced into booting from NOR flash - but the link goes to an empty page! Perhaps there info elsewhere on the web that explains how to boot your device from the NOR flash. Then, I assume the standard system upgrade would work. Sorry
  13. @just.in.time That looks like the same package I used. Do you know if your GL-AR300M is the cheaper version with Nor Flash memory, or the better one with Nand memory? (models are here) Mine is the cheaper GL-AR300M16-Ext which uses Nor memory. The reason I mention it is because in the OpenWRT packages there is another folder called nand, which I wonder is for devices with Nand memory? https://downloads.openwrt.org/releases/18.06.4/targets/ar71xx/nand/ You could perhaps try this file? https://downloads.openwrt.org/releases/18.06.4/targets/ar71xx/nand/openwrt-18.06.4-ar71xx-nand-domywifi-dw33d-squashfs-sysupgrade.bin
  14. @Michael_b @10001001sos I just did a quick test via the Network Software Selector to switch from Open Transport to MacTCP - and I was able to replicate the problem. And I was using system 7.5. So I don't think it's to do with System 7.1 but MacTCP - I'm looking into it. In regard to some sites not working in MacWeb, I believe @Dog Cow is correct. From what I've read MacWeb did not fully implement the HTTP 1.0 specification, meaning many modern website will not work. It's not so much about the web pages themselves, but the web server that they are being hosted on. See this article: The MacWeb developers apparently took a look at the HTTP 1.0 spec, decided, “Who would ever need name-based virtual hosting?” and left out the feature that 99% of the sites on the modern web relied on. No support for virtual hostnames meant you got whatever you saw when you used the server’s IP address alone in the HTTP request, and for most sites, that was jack squat. Oh, and HTTPS, cookies, and CSS hadn’t been invented yet. I'm also able to replicate the HTTP 400 error you see using a web debugger, by setting the HTTP version to 0.9:
  15. Hey @Michael_b thanks for the info, that's great that you got the extension running on an iMac! I've not been able to test that. I'll need to do some testing on System 7.1, or perhaps add some diagnostics / logging so we can see what's happening on your Mac. I'm also wondering if it's MacTCP vs Open Transport - as I've only tested on systems running Open Transport. Bear with me, I only get a few hours of geek time each week but I'll try and help you out. I'll also look into your stunnel config.