Recent Posts

Pages: [1] 2 3 ... 10
1
DAW - PowerPC OSX-based Applications / Re: Look for Pro Tools 6.4.1 TDM
« Last post by Syn-Fi on Today at 04:34:30 AM »
hi mr happy,
no the inferface, an 888, is definitely hooked up and it works in OSX with CoreAudio - so its definitely hooked up and working. It also works in OS9.

the problem i have, is that the interface is not seemingly picked up with Protools 6.4.1 and there is no obvious explanation given the above.

Note CORE audio is not running when i launch Protools 6.4.1 ...the CoreAudio app only launches when i use Bias peak and TDM h/w and interface.

Any further ideas?

looked at the reference guide already and given the H/w is working it is a software/config problem and thats why i have posted up here to see if anyone else has resolved it.
2
An emulator could do MIDI, I know almost nothing about audio, tell me what type of device you are using in you mac for MIDI.

A PCI card?

A USB to MIDI?

Serial port ! of course. outboard midi processing unit connected via Serial RS-422.

Qemu supports USB passthough:

https://www.connectivitycenter.com/usb-to-serial-adapter-9-way-rs-422-1m-42844.html

Tho the FPU of qemu-system-ppc needs a lot of work, as does the Vec unit. I would guess that audio work hits the FPU pretty hard, so until someone fixes that up, it wouldn't do you much good.

A few years down the road........
3
Mac OS 9 on Unsupported Hardware / Re: Booting Mac Os 9 on Mac Mini.
« Last post by darthnVader on Today at 02:37:25 AM »
Quote
Does anyone need to see NanoKernel Logs from my Mini or are we past that stage now?  If we don't need it anymore I'd like to be able to boot this ROM with the function disabled so it quits getting in the way.

I too was wanting to disable this, you can close it with Command+F2.

There are a couple of resources in the ATI Graphics Accelerator that have the Device ID for the 9200, make sure you change them all.
4
An emulator could do MIDI, I know almost nothing about audio, tell me what type of device you are using in you mac for MIDI.

A PCI card?

A USB to MIDI?

Serial port ! of course. outboard midi processing unit connected via Serial RS-422.

5
Mac OS 9 on Unsupported Hardware / Re: Booting Mac Os 9 on Mac Mini.
« Last post by MacOS Plus on February 24, 2018, 09:33:55 PM »
  No luck on the 2D acceleration yet.  I don't know if I'm doing it wrong or if something more has to be changed.

  I do have one minor thing to report on related to the Finder crash and warning message about missing system software.  (The exact text of that message was as follows - "Your computer can't sleep because some system software is missing.  Reinstall the software that came with your computer.  [Shut Down] [OK]")  Just to see what would happen, I did the "screamer" OF edit to the sound device using the commands from one of the iBooks.  The Apple Audio Extension no longer crashes the boot with this change in place.  Oddly though, the Finder crash and the missing system software warning at the desktop also went away.  The sound device itself doesn't appear in the Sound control panel though and obviously doesn't work.  Perhaps this experience will help someone sort out how to correct it properly though.

  I'm still really curious about why the AppleTalk control panel reports "Modem/Printer port" available and doesn't complain when I select it and save the setting.  System Profiler doesn't know the internal modem is present, but even after physically disconnecting the modem card from the motherboard, some other device is still recognized as this 'phantom' serial port.  I'd really like to know what's going on here and whether or not this means I could hack in a true serial port in place of the modem or via whatever other data path this detected port is showing up on.  You'll recall on the 9serve that I had to use the Stealth driver to make the built-in serial port appear to AppleTalk.  Serial ports only show up in AppleTalk without 3rd-party assistance if they are physically present as a standard serial device (or perhaps emulated, but I think that's unlikely).  I find it hard to believe that I'm seeing a 'false positive' here.  Is it a populated debug port?

  Another thing I'm wondering about is to do with the USB ports.  System Profiler reports three USB ports present - Ports 1 and 2 are the external ones, while Port 0 which comes first I can only assume is for the bluetooth card.  My Mini doesn't have the mezzenine board for Airport/bluetooth, so I can't prove it.  The bluetooth card that would go in a G4 Mini appears to be the same one that is in the MDD.  I've seen a reference online showing which pins are the USB data lines on the bluetooth connector, and the implication is that you could probably get a functional extra USB port wired from here in place of the bluetooth.  You just would have to pull the USB power from somewhere else, or at the very least dedicate a powered hub to this connection.

  Does anyone need to see NanoKernel Logs from my Mini or are we past that stage now?  If we don't need it anymore I'd like to be able to boot this ROM with the function disabled so it quits getting in the way.
6
DAW - Vision & Studio Vision by Opcode / Re: Drum matrix weirdness
« Last post by Syntho on February 24, 2018, 08:50:21 PM »
https://www.youtube.com/watch?v=rwfX0k-fqK0 - a little into the video the guy uses an SC-88. The note names window works fine in the video. I added an SC-88 to OMS and tried it in SVP but it still gives me the same '...'  ??? I also trashed the preferences of SVP but that didn't help either. EDIT: And booted up another Mac using System 7 and I get the same thing. SOMETHING is going on here...
7
DAW - Vision & Studio Vision by Opcode / Re: Drum matrix weirdness
« Last post by Syntho on February 24, 2018, 08:27:17 PM »
With your files, the note names show up in the tracks list once selected, but again it doesn't show up when you click that field to select the note. It has a bunch of '...' for every custom note name.

I think I'm just continually finding little bugs here and there that Opcode never fixed. I tried selecting another drum module and entering custom note names but it's the same thing: it shows up once selected on the left side as usual, but when you're actually looking in the list of drum notes after click-holding in the note field popup, it's just '...' for everything. Or maybe it's not supposed to show up there in the first place?
8
HELP BOARD ! Installing & Troubleshooting the Classic Mac OS / Re: File type not correct
« Last post by GaryN on February 24, 2018, 04:14:38 PM »
It appears that this was not a dead battery either. It looks like after something caused the machine to boot to OS9, then slight differences in the file properties caused the Quickbooks datafile to be unreadable as well as the date/time. Whatever made the machine startup on OS9 was static for weeks until a crash, after which it booted on OSX (10.2 Jaguar) where everything is back to normal. Even the date/time is set accurately (which I had never manually reset on OS9).
I got curious and dug into your issue. You should read this: https://www.macworld.com/article/1002820/QuickBooksPro5.html

It points out how QB5/Mac is is crap version with lots of problems. it was evidently not much more of a carbonized version of QB4 - carbonized so it would run on either OS9 or OSX. It's not surprising that despite that alleged ability, it evidently can't recognize its own files on one OS or another. Couple that with the fact that 10.2 is hardly a perfected OS itself, and anything can (and apparently does) happen.

You also almost certainly do have a dead or at least a very weak battery. The startup system selection on dual-boot machines is one of the parameters held in PRAM, and PRAM requires a working battery to hold data reliably. The fact that the computer reset its own time/date is a feature of OSX you evidently aren't aware of.
Any ideas on what really happened? Or how to prevent this in the future. Can I delete OS9 from the machine entirely so it can't ever boot there? Or some better idea?  (Since I won't be using the machine again until tax season next year, I may forget again what the correct OS version is. Although going through this this year will probably make me remember.:)  This machine will stay on OSX 10.2 as long as it keeps working.)
As explained above, what happened is you have an old computer with old OS's and an old battery incapable of maintaining the settings for a whole year. To answer your questions:
1. You can absolutely delete OS9 entirely by simply locating the OS9 System Folder and deleting it. This will cause you to be dependent on 10.2 so you better make sure that everything you need works in OSX first.

2. The best way to prevent this in the future is to not leave your tax returns entirely dependent on an ancient piece of crappy software running on an old operating system (that I wonder if you have any original discs of) sitting in a closet depending on an old battery……do I really need to continue?

Some observations…
Tax returns are a pain in the ass.
Having tax software is supposed to lessen that pain.
Computers and applications and data need to be maintained - at least minimally if you want it all to work when you're staring at April 15th.
Almost nothing will cause more unnecessary grief in your life that f**ing up your taxes.
Quickbooks 5 is was a lousy app to begin with and is now completely obsolete.

At least, get a new PRAM battery, backup your apps and data and consider updating your tools a little. You never said exactly which old Mac you're using, but at least updating it's OS to something newer than 10.2 would be a prudent move.
9
i just went thru a similar issue with my B+W G3.. the year was set to 1970 something somehow
and i was surprised that, via the date + time control panel, i was able to sync to time server still.. in 2018!
which set the proper date/time
10
HELP BOARD ! Installing & Troubleshooting the Classic Mac OS / Re: File type not correct
« Last post by mb66 on February 24, 2018, 01:36:24 PM »
It appears that this was not a dead battery either. It looks like after something caused the machine to boot to OS9, then slight differences in the file properties caused the Quickbooks datafile to be unreadable as well as the date/time. Whatever made the machine startup on OS9 was static for weeks until a crash, after which it booted on OSX (10.2 Jaguar) where everything is back to normal. Even the date/time is set accurately (which I had never manually reset on OS9).

Any ideas on what really happened? Or how to prevent this in the future. Can I delete OS9 from the machine entirely so it can't ever boot there? Or some better idea?  (Since I won't be using the machine again until tax season next year, I may forget again what the correct OS version is. Although going through this this year will probably make me remember.:)  This machine will stay on OSX 10.2 as long as it keeps working.)
Pages: [1] 2 3 ... 10