Search results

My dad is a boomer and the Mac Plus was his daily driver for years so it's technically correct. However, I also grew up with it and you can't classify me exactly between X and millenial so take that as you will.

It looks incredible. I'll put this in my real machines because it'll be more than worthy! And I'm truly sorry to hear about your mother and the hard past year your family has had. You have my condolences.

That would be the deep end for me, but it's a very, very cool and dangerous idea. It just don't fit in a 800kb disk though, I had less than 50kb free on my disk here.

Here's the video about it: thanks again everyone, it would have been 5x more painful without your help to get to the finish line.

Found it! FillRect works again (magically, can't explain it) My anti-pop code had an offset written like 36/4, which puts it at an odd number of characters offset (9), changing it to 32/4 made it even again, satisfying the alignment when playing the sound data.

Nope, it's the curse that keeps on giving. I'm still on the version that worked before I went to bed, before I fiddle with FillRect again. I'm trying to boot it with a 800kb dsk under mini-vMac, no issues with System 6.0.3. On a hardware mac though, the same .dsk with FloppyEmu (or copied on a...

I've tried and failed over a hundred combinations with small tweaks. I'm willing to try (retry?) yours for science's sake and post the result. It's hard to find the motivation to document every attempt when fatigue enters play after hours. Edit: I have to say, that's a fine piece of code there

I got it. Had to do the A5 fetching and setting Had to receive the quickdraw globals in a custom made struct as per that last article so I could get to the baseAddr of the screenBits. Doing InitWindows to display my own plainDBox white featureless window was a no-no because it requires...

InitGraf alone:

Yes, I tried the trio of InitGraf, InitWindows and doing a NewWindow, got the coprocessor error. I just tried blanking out the screen 1 char at a time and I'm going sideways now:

On a hunch, I decided to comment out all the DrawPicture calls and kept only the white pattern FillRect and I got this: HMMMM

One of the things I explored is: should I initialize a window before drawing to it in the INIT? But I get messages like these (coprocessor not installed... ??)

New roadblock. I've taken ALL the precautions to make sure my PICT is exactly 512x342. My INIT will scale it up weirdly and show it thus: and when I'm all booted up seconds later, I've run another normal app that opens and draws the exact same PICT resource (I just duplicated it across .rsrc...

Living dangerously when prototyping! But yeah, don't worry, I checked that something was loaded in the debugger, that was my first reflex.

and the w95 sound works! but it's 2x too fast......I should have trusted Audacity.

I have to force a delay, don't I? I thought I was playing the sound synchronously... edit - yeah, the piano sound works now! just had to add: while(!SoundDone()); StopSound();

The buffer padding anti-pop trickery was swiped somewhere a long time ago. I can't find the source of that trick for now... edit - I know that SysBeep is there and StartSound is commented out, I just forgot to change it back. It doesn't work either when it's properly changed back.

After a bit of scrounging for old source files, I successfully: 1) ran code that uses the Sound Driver to play a .snd resource (piano sample from Studio Session) that I pack in a regular application. hear it fine in System 6 in mini-vMac when I launch the app. 2) prepared my other INIT project...

I've used THINK Reference Viewer forever, don't worry. I've seen that section last night.

I'm reading this extensive mactech article: http://preserve.mactech.com/articles/mactech/Vol.05/05.10/INITinC/index.html in the hopes of doing a cursed booting INIT. This time, I'm targeting ease of use and focusing on System 6 only, maybe add System 7 later. But my idea would be slightly...