Jump to content

Cory5412

Administrators
  • Content Count

    8459
  • Joined

  • Last visited

6 Followers

About Cory5412

  • Rank
    Daring Pioneer of the Future

Contact Methods

  • AIM
    Cory5412
  • Website URL
    http://www.stenoweb.net/

Profile Information

  • Location
    Arizona, USA

Recent Profile Visitors

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

  1. Cory5412

    Apple Watch burning a CD.

    . Before I hide these and/or lock this thread: Did this come entirely out of left field or were these responses supposed to be for a different thread, or?
  2. Cory5412

    AppleTalk net cable

    Yeah, either APple's own localtalk adapters or the phonenet adapters. And, the advantage of phonenet is absolutely the cheaper and easier-to-get wiring. Apple's own wiring system has some neat functions - like, you don't need special terminators or to complete the loop, and you can leave unoccupied boxes in spots without the network going down. Here's the user guide to the Apple's wiring system: https://vintageapple.org/macmanuals/pdf/Apple_LocalTalk_Cable_System_Owners_Guide_1987.pdf
  3. Cory5412

    Is the Wiki dead?

    By the way: The above probably sounds like I'm laying some or all of the blame for the wiki's inactivity on the community itself. There's a kernel of truth in there, because ultimately wthww can't author everything ourselves, but I want overall to express that I'm very happy with where the community is at large. I think if it was something I'd had the time and energy to work on, things would be different, and getting the wiki into better shape is something I want to do. I do want to reiterate that we don't need design or programming, largely, beyond the "decide what to even do" phase, the things we need to do will involve writing, copying, and organizing. I'm open to ideas if people think there's better ways to do these things - i.e. if a switch to dokuwiki or MS SharePoint or whatever would serve the community better, just be aware that that kind of switch is going to result in an audit of the articles and a content migration, and we might not be able to automate it. The biggest technical problem with mediawiki as it stands is the user management and spam control problem. Our previous wiki activist community member had been given sysop privs and was doing the user management there for us. THat's kind of a sunk cost regardless, because switching to a new wiki tool doesn't remove the need to do that, even if it makes it easier. The things in the first post above are very "low hanging fruit" kinds of article. Some (many, even) of them are already written, it's just a matter of adapting a stickied forum post for wiki consumption and then as an admin action, possibly finding and replacing links to that thread to the actual wiki article.
  4. Cory5412

    Is the Wiki dead?

    The wiki is not dead. There are a handful of issues, and to be honest this is something wthww and I need to just sit down and decide and do, but both of us have very busy lives already, so the wiki falls by the wayside. The first is that MediaWiki has very poor user management, and that I don't want to integrate Mediawiki with Invision, for sign-ons, which we did in the distant past when we had PHPbb2. This is mostly because I'm not skilled at modern webapp/linux security or PHP tools in general and I want maintenance to be as simple as it can be. The second is that, because of that, user management is currently totally manual. This is to prevent defacement and things like those bots that used to run around and create pages on random wikis they found online, alternatingly for storage and for advertisement/google algorithm gaming. The third is that we got the new CMS/Forum and I wanted to use it, but as mentioned, there are some shortfalls with invision that make that difficult. I last reviewed the forum's articles functionality on a fresh local dev install in 2017, so it's worth looking again. I believe there's been a couple new feature releases since then and so it might be much better now than it was back then. The other thing is that maintaining a wiki is less about programming and more about culture. The software itself is more or less in good standing, other than having a "dated" visual design (fine, TBH, it's there to house information, not to look pretty) and the person who built out most of the pages left a couple years ago. I've been toying with a local copy of dokuwiki on one of my computers at home and part of what I was thinking about there was "what would make a good macdex" - thinking about how the editorial style of Low End Mac might be useful for containing relevant information or links to relevant information on a page, but keeping the formatting pretty consistent, and ideally also combining families of machines on a single page. (So there's a single "6100" page, not 12 unique pages for all the different configurations plus performa and WGS variations.) The thread with article ideas is here: Much of what I've put in this thread is stuff that we already have in stickies, or information that was sourced elsewhere as part of regular proceedings around the forum. jt put a handful of things in about architectures, for example. This isn't itself a comprehensive list of what needs to be done, but, more like a to-do list. We're now entering the worst part of the year for me in terms of forum/wiki work, because I'm a local organizer for nanowrimo, and in november I'll be doing that and writing a novel, so I'm likely to cut back on forum time a lot. So, overall: The wiki is in a technically sound state Protecting MediaWiki from vandalism amounts to either constantly reverting changes and deleting spam pages, or manually managing users User management in mediawiki is bad. I would argue it's outright broken. We need to see if Invision has gotten better enough The issue isn't programming or programmers per se, but rather: people willing to author, edit, source, and organize content, plus deciding what projects we as a community want to handle. For example, is it worth our time building or maintaining a "macdex" when there are already so many of them out there? If we move to a new system, we will likely need/want people to review the existing content and re-author it for the new system. As part of that process, we should probably give consideration to what articles can be removed. Again, other than deciding what to do and then doing it, the most important thing, the thing we'll need the most hands involved in, is going to be migrating and/or writing content, most of which will involve transcribing forum posts. The long game is to build interest in the wiki as a community project, and not just as "so-and-so's" project. The gotcha here has always been scenarios where people wanted complete control over a particular page, or just failure in general to get people interested in the idea of a wiki, especially from back before we had to cut down on post editing. *(Most of our stickied posts are from when all users had indefinite edit capabilities, for example.)
  5. Cory5412

    AppleTalk net cable

    Very nice! I extremely want to do something like this. Backyard/neighborhood LAN is an aesthetic I hold very strongly and would extremely love to do at some point. Somewhere there's an official spec for how long an AppleTalk segment can be, and my favorite thing about it is that using a repeater/concentrator doesn't actually introduce any forgiveness to that max length, but bridging two segments with a Mac or with two ethertalk/localtalk bridges should. (I don't know if there were any routers with more than one localtalk connection, that wouold probably reset the distance.) I don't know if LocalTalk is like DSL technologies (SHDSL in particular) where you can just keep stretching the length at the expense of sync speed or if there's a point at which it cuts out.
  6. Cory5412

    Quicksilver zip-drives

    This machine is not really a unicorn. It was a factory option from apple. If you want it, it looks like a pretty okay deal, but it's not really important per se, and you can use a ZIp without the special bezel, it just looks less good. It's tough to guess how many actually shipped that way because it looks like it became a BTO option as preferences shifted away from Zip toward burning CDs/DVDs and using USB-based media. So, it definitely appears to be less common here than in the previous chassis (which was used for three or four generations of powermac). My QS'02 has it, but. Incidentally, looking through on wayback captures of Apple's site, it looks like Zip became a BTO option as of either the Gigabit Ethernet family or the Digital Audio family, which was probably good since Zips had been holding up high end Power Mac shipments since literally Apple started bundling them in 1997.
  7. Cory5412

    Solid State Drive for G3?

    This sounds a little bit like something that happened with mine. I'm trying to recall because I didn't write it down, but, it was either when I installed a mis-configured SCSI2SD with wrong termination settings or when I installed a faulty hard disk drive. Did you end up using the OWC SSD or on a SCSI2SD?
  8. Cory5412

    Daniël's Conquests

    This is an error we know about. When wthww has an opportunity, whatever's causing this will be fixed. Uploads directly to the site should be fixed at that point as well. Some more information is available in the site bug-tracker thread in the lounge, starting with this post:
  9. What are the loadouts on each and what all stuff do you have already? To be honest, the 475 is a perfectly serviceable machine. It's the same speed as a Quadra 700 and it can take less VRAM than a 700/900/950, but it'll still output to an 1152x870 display and you can clock them up to 33MHz, and you can add "full" 040s to get the FPU, which isn't beneficial for much, but it might be beneficial for a software dev workflow. You'll also need to account for an LC-PDS Ethernet card in a 475, which the 700/900/950 have onboard, but those machines also need an AAUI transciever. Other than that, the advantages of a 900 are that it's got a lot of slots, a higher memory ceiling, and a 5.25 bay, which might have a CD-ROM drive in it. A 475 will be able to use an external scsi cdrom drive, however. It's pretty hard to go wrong in this era, but what specifically you want can guide what you might look for. Other good machines are the 630-640 series, which has a CD-ROM drive but can only do 832x624 video. The 650/800 are sort of the successor to the 700, they both support CD-ROM but not all of them have it, they've mostly got onboard Ethernet (there are some 650s without, though) and they have varying CPU configurations, mostly with full 040s. The 840 is also good, slightly faster stock CPU than the others, but it lacks the 950's RAM ceiling and the 800's memory interleaving, so if you want a top end machine, picking the one whose particular go-fast stripes match what you want to do. Overall, of that group, my recommendation probably falls to the 475, provided you either don't need or can budget for adding things you want to it. (ethernet, CD-ROM in particular) If you don't clock it or accelerate it you'll wait longer for, like, builds, or other "compute job" types of things, but day-to-day I don't know that i think you'll notice the difference between 25 and 33MHz, especially in system 7 and especially if you aren't multi-tasking or running background work like a chat or IM client. (For example, I had an 840av in 2002 or so I was using as my daily internet system, with 64-72ish megs of RAM. I probably benefited over a 25-33MHz system because I was running AIM and Outlook Express in the background most of the time.)
  10. A 950 will have shipped with 7.0.1, so if you want that version, get, or find the diskettes for it online. If you want early 7 but don't want to bother finding the 950's diskettes specifically, a 7.1 or 7.1 pro set should work fine. If you want a newer OS version anyway, then other media will work. If you have an opportunity to get the original install media, I personally recommend taking it just because that kind of thing is nice to have.
  11. You can also use retail CDs or floppy sets for 7.5.0 and later. If you have 12 megs of RAM or more, 7.6.1 or 8.0 will also work on this machine. I've got some ISOs you can burn on a modern computer here: http://personal.stenoweb.net/oldmac/ macos761retail and macos8retail would be the best images for that. imac233-81 would also work.
  12. Cory5412

    AppleTalk net cable

    LocalTalk is itself a ring network design, physically, even though it won't work to create a bunch of multihomed 2-machine LANs. Regarding distance: Apple's own Localtalk wiring kits can achieve the same distance PhoneNet can, it's just that serial cables are typically only six feet long. (I have seen a couple longer ones, which would be nice for a couple different scenarios.) There is a localtalk bridge tool and AppleShare and ASIP server machines are supposed to be able to multi-home AppleTalk, so if you were using a beige Mac as an ASIP or AppleShare box, that could be a way to have some flexibility. The other thing is, if you have an AppleShare IP server and some newer clients, you can use that server on ethernet with IP and turn AppleTalk to a serial port for local. (I used that method with my beige G3 to move files from vtools to my PB1400, for example.)
  13. Cory5412

    Tanzania to Tanzania II upgrade

    The reason I want a 6500/300 specifically is because I want to compare 603e performance to 604e performance and G3 performance. I wouldn't mind grabbing a 300MHz G3 chip for my blue-and-white either just to add a fourth datapoint, mostly to show how much platform enhancements help. I already have an 8600/300 and a Beige G3/300 and the Beige G3 outruns the 8600 by a country mile. If you don't care about adding certain PCI cards, the easier solution is to get a 6500/225 or /250 (I'll argue that /275 and /300 boards should be left alone) and put your G3 upgrade there. It sounds like the big hang-up with the 6500 might specifically be ATi video cards (because it has an onboard Rage II variant) and multi-function cards (like the tempo trio, which jt likes because of its multi-functionness.) I haven't seen (or don't remember) notes about just-SATA or just-IDE in the 6500, so that might be A Thing to be aware of.
  14. Cory5412

    Solid State Drive for G3?

    The 12-inch color monitor does 512x384, and the 12-inch grayscale display does 640x480. I'm around 90% sure system 9 will recognize and work with both on built-in mac video.
  15. Cory5412

    Fast 601: PowerComputing Power120

    Very nice sounding setup. My system has a very flat looking heatsink. I've got some thermal interface material around, so I'll look into pulling it off and cleaning that all up and re-applying it. I don't really intend to put a lot in it in the way of cards - an HPV card will probably be it for me. I'll also look out for that second battery. I do see the original PRAM battery in there and I'm presuming it's dead. Just gotta find my stash of replacement PRAM batteries. If the coin cell is a 2032, I'll pop that out and put a fresh one back in, as I have a supply that goes with another gadget I've got. One other fun note is that the machine came to me without a CD-ROM drive installed. I'm quite tempted to leave it that way, although thinking about it I do have a SCSI CD drive somewhere. (Perhaps i should put that drive in the enclosure from an 88-meg SyQuest drive I have). I'm extremely entertained to imagine the kind of person who would have ordered a 120MHz PowerPC system in 1995 without a CD-ROM drive. Once the machine boots: As a more immediate work-around, I'll probably make a copy of the 7.5.3 network access disk, hope it boots on these machines, and then mount a CD image on vtools and install an OS that way.
×