Recent Posts

Pages: [1] 2 3 ... 10
1
Virtual Machine & Emulation / Gamepad controllers?
« Last post by nd2003grad on Today at 04:47:52 PM »
Hey there...I just installed a "buttload" (technical term) of emulators and have been playing around.  I have a cheap Chinese PS1 knockoff controller that works like a dream on PC...but...its buttons seem to be recognized incorrectly by OS9.  I have a goodwill that has a ton of cheap controllers.  I really like this one, but does anyone have suggestions (we're talking like NES etc emu)?
2
Mac OS 9 on Unsupported Hardware / Re: Booting Mac Os 9 on Mac Mini.
« Last post by nanopico on Today at 02:48:52 PM »
Would somebody (looking at you nanopico) please post on how the mini's USB controller differs from a supported G4?

I'll look, but it really doesn't.
It's the PMU.  It is controlled over USB.
They will be tied together nicely (or not so much).
That is why the both need to be disabled.

PMU99 (supported) is a Mitsubishi M16C/62F microprocessor.  It uses it's own RAM and ROM.  the uPMU in the mini will likely not have the same ROM and thus not the same interface (from a communication/software standpoint) except for very very low level common functions like turn on and turn off. 
Intrepid controls all IO (USB and PMU communication). The USB controller chip and PMU are known for all the supported and other machines.  The communication through Intrepid is obviously slightly different than the straight up Keylargo chip used elsewhere or else the PowerBooks would have much more  functionality.

So details on uPMU and Intrepid are needed.  There is much info availble in the OS X source to help identifiy the difference between Keylargo and Intrepid. I have found nothing directly related to PMU99 or uPMU in the OS X code (it's a lot so it's not exactly fast to go through).  All power IO does appear to be handled by Keylargo or Intrepid.  So those chips definitly have knowledge of communication to the PMU.  Disabling the PMU and USB controller makes intrepid stop using them so it just goes on it's happy little way.

Okay I'm starting to confuse myself.  I'll dig more when I get a chance.
3
This thread has become very confusing BUT:

Ralphieboy: Have you tried / you should try removing the Sound Manager driver from the Ableton ASIO Folder - have ONLY the M-Audio ASIO driver in there. Easy to try and just might…
Requires a restart.
4
Hoi, i have a few Lacie Quadra cases (FW400/800, usb2 & sata) with 2TB drives and an older FW/usb case (500 GB pata/ide hd build in). On my QS867 booted in os tiger or leopard I can partition (apple partition + 0s9 drivers) the FW-drives and they are bootable under OS9 if partitions are small enough. Oddly it seems you'll have to make ten partitions (189Gb each) on the 2TB drives to get them small enough. At first sight I couldn't make one small (sliding in drive setup stops at 250 something) and a few larger (+500GB) partitions on the 2TB drives.
So if you have a dual boot machine this looks to be the easy way ...
5
I experience some problems with a M-Audio Firewire 410 audio card.

- The level controller knob has no effect on volume output.
- Output sound is awful: very low, saturated, seems out of phase.

Can you see firmware number from M-audio Control Panel?
6
Statement from another site (http://www.oldschooldaw.com/forums/index.php?topic=27.0):

There were 3 Studio 5 ROM releases:
10/11/91 - original release: This release did not support networking.
10/13/93 - LX release: This release supported networking. Much code was optimized resulting in better performance, and numerous bugs were fixed.
8/15/95 - LX maintenance update: This release fixed a few minor bugs: One was the 100 protocol numbers bug.
(click link above for more)

Btw.: They already added a related firmware download link as well from their site some days ago, especially after they realized that mmtuk provided his ZIP archive here at this place  :D

As we all know, Opcode was killed later on by Gibson.
I'm very sure that the 1995 maintenance release was the very last firmware officially released for the Studio 5 LX, as I've been looking for that ROM dump for years now.

Additional hints for firmware programming & device setup:

Two pieces "27C256" EPROMs are necessary. Of course you can also use so-called OTP (One Time Process) PROMs of same type in case you don't intend to erase/re-use these memory chips later on for other purposes. At least OTP-PROMs are a little bit cheaper than EPROMs.

Another option is to use "27C512" EPROMs/OTP-PROMs instead (if you want to waste more space/money). In this case two jumpers on the Studio 5 LX mainboard must be set differently. Positions are clearly depicted on the board, so nothing can be done wrong.
7
It may make a difference if the FW unit is connected and switched on during boot and which FW extensions are active. Fingers crossed :)

I don't understand quite well this one. Can you explain please?

he was repeating / echoing what i said about the correct procedure to connect the device to a mac/pc
u cant just plug it in when the computer is on u need to turn BOTH devices off.. then connect the fw410 and power it on BEFORE turning on the computer..

adding that there are different firewire extension versions, and to experiment with different versions
maybe we need another thread with all the firewire extensions posted?

honestly its most likely that the device is partially damaged; alot of people end up frying the m-audio firewire devices by hotplugging them; not understanding that these old interfaces + their firewire connection are not hot-pluggable like a usb device is
8
Quote
2) I use M-Audio Firewire 410 ASIO driver with Ableton Live 1.
Anyhow, I have the same thin and poor sounding when I play an audio track with iTunes thru the M-audio Firewire 410.

Again, try all ASIO drivers available, Versions 1 & 2, and restart the app each time

also, try NOT routing System sound so no itunes for now; try getting the ASIO by itself working first
9
It may make a difference if the FW unit is connected and switched on during boot and which FW extensions are active. Fingers crossed :)

I don't understand quite well this one. Can you explain please?
10
I experience some problems with a M-Audio Firewire 410 audio card.
- The level controller knob has no effect on volume output.
- Output sound is awful: very low, saturated, seems out of phase.
I use a TiBook 867, the card driver has been installed, have tried different cables and my monitor speakers are not responsible of the problem.

OK, so a few questions...

1) The TI has FW built in, are you saying you are using a FW Cardbus like an Adaptec "Fire Connect" or other model in the Cardbus slot of the TI ?

2) Also, are you using an ASIO driver with the DAW application ?
And if so, try a different ASIO driver, Some apps like certain ASIO drivers over others and can cause the issues you are describing

Hi DieHard.

1) I was refering to the M-Audio Firewire 410 Driver (in France will call such devices "Audio Cards"). I use the built in FW port. The CardBus slot is empty on my machine.

2) I use M-Audio Firewire 410 ASIO driver with Ableton Live 1.
Anyhow, I have the same thin and poor sounding when I play an audio track with iTunes thru the M-audio Firewire 410.
Pages: [1] 2 3 ... 10