Holy smokes this thing zips on my se/30 (using frogfind to access wikipedia pages) with 7.5.3
Netscape asks for 4+ MB of ram but man does it pay off for web browsing over the leaner MacWeb!!
Ordered 64MB today as Ive been meaning to beef up the /30.
Great stuff!!
Really awesome stuff -- Soldered a pico W on myself and I used the MacTCP way (no open transport) for both System 6 and 7 on my SE. I'm going to try it on my SE/30 as the 4MB of ram on the SE is just a tad low to reliably browse wikipedia articles using MacWeb.
The DNS settings weren't happy...
Ok now I (cheaply) hooked it up to the activity LED on my raspberry pi so it makes the hard drive make noises when the activity light flickers.
Gotta say it’s sweert—- next I’ll do this on my blueSCSI and put the drive back in my mac and get that miniscribe feel with blueScsi speed. @eric -...
Tweaked it and made a few functions to emulate the sound of hard drive initialization and then bootup.
i set the audio recording to a few stills of a mac starting. I think it sounds alright!
Why? To hear the miniscribe sounds while I use my blueScsi
wtf? My miniscribe never worked and I gave up on it, so I figured I’d try to drive the stepper motor with some modern circuitry with the hope being that one day I could signal it by the activity indicator on a blueSCSI.
how’s it going...
Found one more thing worth noting here for future aspiring colorists:
For the case when the screen is set to a color mode but I'm trying to get an app's icon using the PlotIconMethod(...,IconGetter,..) methodology - It will call IconGetter twice (as discussed in my recent wave of posts), once...
v1.3 released.
Edit: v1.3.1 released.
See MacDock git repo.
This release adds color! But still faithfully supports b&w screen bit depth as well.
A *lot* of the conversation for v1.3 was held over in this thread all about working with color screens. It got pretty meaty... I really didn't...
Thanks for confirming! I had no idea someone had code like this out there.
And yes I hear you loud and clear on how the code assumes the buffer for the icon has its second half with the mask. This is quite interesting (funny?) because from what I've read in Inside Macintosh indeed the mask...
I had some really bizarre issue --
Unless I call NewHandle(s) inside of IconGetter() function, the resulting plotted icon would have some artifacts (white streaks on the otherwise correct icon). I was trying to call NewHandle just once way outside in Main() knowing that I'll be using that...
Quick reference for those future readers:
@Crutch mentioned Tech Note #306. I found Apple still has these old Macintosh Technical Notes on their developer website. Here is Macintosh Technical Note #306.
I searched using this page but sadly I couldn't find it by searching "tech note #306" or...
Also -- weirdest thing but your demo app (and my similar approach) ends up calling the IconGetter() function twice per PlotIconMethod(). Inside Macintosh says this should happen once per screen that intersects the rect you're working with -- I only have one screen so I'm a little confused by this.
Yes. And I keep calling ReleaseResource(myHandle) instead of DisposeHandle which is probably my gateway to fudging up things. Perhaps I should be more surprised that I haven't fudged up the resources in any of my other applications I've run in my testing...
Thanks.
Wow - as I was messing with all this and the memory leak and Releasing resources I managed to damage my Finder (and more?). To the point where the Finder's icon suite was messed up and so was its reported ProcessType. Very funky stuff. I'm guessing the memory I was releasing or writing to...
Ill be there showing off my app for System 7, MacDock! J/k but I will try to fly out if I can make low cost arrangements.
Actually it’d be cool to see the wifi blue scsi stuff so I’ll keep an eye out for you all.
I’m also hoping to snag an imagewriter if I see one on the free area table
One thing I don't get about the above code is that if I write an app where I have to use this PlotIconMethod(....,IconGetter,...) function a lot, there is a memory leak. Because you call NewHandle(...) but never ReleaseHandle() or ReleaseResource().
I'm *not* criticizing your code, but rather...
Did you just have to recap the analog board (to get to current samasi mac state)?
bet you it is a mux issue. Next recap the motherboard, it no change then check muxes?