image description


Firebox & Windows 7, weird problem
  Forum Index » Firestudio - Legacy 
Author
Message
bradallen
Prenoob

Joined: 10/11/2013 12:03:34
Messages: 2
Offline

Hopefully this is the right place for this - it's a legacy fire___ product anyway. I posted before in the "How do I..." section. Hoping I'll have better luck here.

I know people have had some issues with the Firebox and 64-bit Windows 7. If I was having those same issues I'd at least have an idea of where to start, but unfortunately I can't find this particular issue addressed anywhere. I've done extensive Googling. My hope is that I won't have to revert to 32-bit and limit the computer's capabilities. It kind of defeats the purpose of having a 64-bit computer.

The actual issue is that I can't get Windows to understand that the Firebox is a sound device. It knows the Firebox is there, and it even calls it "PreSonus Firebox" in Device Manager, but it's listed separately as 61883 Device Class rather than with the sound controllers. Windows thinks the device is working properly, even if it doesn't know what kind of device it is; it knows the driver is installed. My studio programs and other programs that give me sound options don't list the Firebox as an option. Oddly enough, the light on the Firebox itself is blue. So, apparently as far as Firebox is concerned, it's communicating as it should. It just doesn't actually do anything. The software for the Firebox installed with the driver. That (either Hardware Settings or the mixer) works fine as far as I can tell, but even Firebox's own software can't find the hardware. It says I have no device for it.

What I've tried:
Installing the driver package for 64-bit from the PreSonus site, as administrator.
Installing the same driver directly from Device Manager.
Installing the old 32-bit driver from the installation CD, knowing it wouldn't work but hoping it might trick Windows into at least knowing what kind of device it's supposed to be, then updating the driver to the 64-bit one.
Switching the IEEE 1394 driver to legacy.
Even though Firebox isn't supported for XP 64-bit, just for grins I tried installing it on a 64-bit XP system with EXACTLY the same results.

I know many people have successfully used Firebox with 64-bit Windows 7, so it has to be possible. I just don't even know how to begin trying to use it if Windows doesn't know what it is. Yes, I'd love to upgrade to newer hardware but it's not in the budget right now. And this thing SHOULD be able to work.

I see this as probably having to do with Windows itself or the driver, since the driver should tell Windows what kind of device it is if it doesn't already know. I highly doubt it has anything to do with the IEEE 1394, since it seems to be doing everything it's supposed to be doing. I don't know of any way to tell Windows that this is indeed an audio device.

My computer itself is more than adequate for running this, so I won't go into hardware specifics unless someone wants to know something. I am, however running a dual boot system with 64-bit XP. I doubt that's an issue though because XP is on a different physical HD, and all its drivers are on that drive.

Any ideas out there? Thanks for your patience.
leomeyer
Prenoob

Joined: 16/02/2014 11:21:38
Messages: 2
Offline

Hi,

I have exactly the same problem, except that I'm using a Windows 7 32 bit system right from the start, so I doubt that going back to 32 bit would solve your problem.

What I did:
- Downloaded and installed FP10 drivers, device shows in Device Manager but Control Panel says "No device".
- Downgraded 1394 driver to legacy. Didn't help.

Device shows as 61883 device but not audio device; I can't select any of the FP10 inputs or outpus in Windows, it's just not there.
Other Firewire audio systems (Focusrite) work quite well on this machine.

I presume your conclusion is correct, Windows doesn't accept the FP10 as an audio device. As far as I'm concerned this could be a driver issue or the FP10 might simply be defective. Considering that I salvaged it from the scrap yard I think this is quite likely. Sorry this does not help you now, I think the only way would be to contact Presonus support or somebody from Presonus posts here with a solution. But this problem seems to be rare (in fact I'm almost sure it's a hardware problem).

Greetings, Leo
bradallen
Prenoob

Joined: 10/11/2013 12:03:34
Messages: 2
Offline

I did go ahead and set up a dual-boot with Win XP 32-bit, and alas, you are correct. Still the same problem, despite this unit being designed specifically to work with XP 32. So apparently this is a hardware problem (or ALL of their drivers are messed up), even though it was working fine on a Mac. At least since I'm back to the old XP I can use my crappy Tascam again, which isn't ideal but at least i have something that works.

Conclusion: Presonus - at least the Firebox line - is junk and I will undoubtedly avoid purchasing anything new from this company when the time comes. Seriously, if a company can't be bothered to support its older products then I why should anyone bother buying its new products? Those will be older products themselves at some point.
leomeyer
Prenoob

Joined: 16/02/2014 11:21:38
Messages: 2
Offline

Well, I wouldn't say the devices are junk per se, though I still haven't got my Firebox to work. I did some more research and found that the problem is actually quite common (device manager says "61883", blue light is always on instead of being red and turning to blue only when the Firewire is plugged in). Somebody traced it to defective capacitors on the board, so I went and checked all the voltages with a scope, but no joy - everything seemed ok; replaced a filter cap but still no luck. Then I gave up as I had no clue what to check next. So it's definitely a hardware problem for me, not a driver issue. I haven't researched it exactly but I presume the Firewire interface chip is still working but the next level, i. e. the CPU with advanced logic, is somehow disfunctional.
Given that the box is from - what? 2005 or 2006? - I'd say, good riddance. Would have been nice, though, to see it work...
If yours works on a Mac, though, that seems strange...

This message was edited 1 time. Last update was at 27/02/2014 16:52:54

cristofe
Presonificator
[Avatar]

Joined: 12/03/2012 21:10:44
Messages: 3628
Location: Skaneateles, NY USA
Offline

If yours works on a Mac, though, that seems strange...


And THAT is a VERY good point.

I've had many Firebox's and Firepods. They are great interfaces and have provided me with rock solid performance.
OFTEN the problem is NOT the interface but rather cheap firewire chipsets used by the PC manufacturers. All firewire
chipsets are NOT created equal. Here is a list of known good chipsets:

http://www.presonus.com/uploads/products/media/files/PreSonus_FireWire_Chipset_Compatibility_7-25-12.pdf


The fact that your Firebox worked on the Mac and not the PC is a VERY likely indication that your COMPUTER is the
problem and NOT the interface!

This message was edited 1 time. Last update was at 27/02/2014 17:47:08


PC'S: HP XW6000 Dual 3.2GHz Intel Xeon Processors, 8GB RAM WinXP SP2
HP 6005 Pro AMD Athalon X2 B24 3.0Ghz Processor, 4GB RAM Win8 Pro
HP Compaq NC6320 Laptop Intel Core2Duo 2.0Ghz Processor 3GB RAM Win7 Ult
Dell Latitude E4310 Laptop Intel i5 2.67Ghz Processor 4GB RAM Win7 Pro x32

Audio Interfaces: Terratec EWS88MT PCI (2), Audiobox 1818VSL USB & FP10 Firewire, Steinberg MI4 USB, Line 6 Toneport GX & PodXT, Roland GS-10, NI Rig Kontrol 3

Monitors: Yamaha HS50M's

DAWS/VST Hosts: S1 Professional, Plogue Bidule, Xlutop Chainer, Sieb VSTHost & Savihost

Hardware Synthesizers: Roland SH-32 & XV-3080 RedSound Darkstar XP2, Novation X-Station, Yamaha AN200, M-Audio Venom

Hardware Controllers: JL Cooper CS-10 Control Surface, Yamaha EZ-EG, Dillion Les Paul style acoustic electric guitar with Roland GK-3 pickup and GI-20 converter.

The Rest: Guitars, Amps, Stompboxes, Mics, Outboard Gear, VST plugins...too much to list!
[WWW]
cristofe
Presonificator
[Avatar]

Joined: 12/03/2012 21:10:44
Messages: 3628
Location: Skaneateles, NY USA
Offline

Ok, it looks like your pc does have a compatible chipset. HOWEVER as your Firebox DOES work on the Mac your
computer is still the likely problem.....probably an IRQ conflict. If you want tech support then you need to open
a support ticket and they'll get you sorted out.

PC'S: HP XW6000 Dual 3.2GHz Intel Xeon Processors, 8GB RAM WinXP SP2
HP 6005 Pro AMD Athalon X2 B24 3.0Ghz Processor, 4GB RAM Win8 Pro
HP Compaq NC6320 Laptop Intel Core2Duo 2.0Ghz Processor 3GB RAM Win7 Ult
Dell Latitude E4310 Laptop Intel i5 2.67Ghz Processor 4GB RAM Win7 Pro x32

Audio Interfaces: Terratec EWS88MT PCI (2), Audiobox 1818VSL USB & FP10 Firewire, Steinberg MI4 USB, Line 6 Toneport GX & PodXT, Roland GS-10, NI Rig Kontrol 3

Monitors: Yamaha HS50M's

DAWS/VST Hosts: S1 Professional, Plogue Bidule, Xlutop Chainer, Sieb VSTHost & Savihost

Hardware Synthesizers: Roland SH-32 & XV-3080 RedSound Darkstar XP2, Novation X-Station, Yamaha AN200, M-Audio Venom

Hardware Controllers: JL Cooper CS-10 Control Surface, Yamaha EZ-EG, Dillion Les Paul style acoustic electric guitar with Roland GK-3 pickup and GI-20 converter.

The Rest: Guitars, Amps, Stompboxes, Mics, Outboard Gear, VST plugins...too much to list!
[WWW]
 
Forum Index » Firestudio - Legacy
Go to: