My Windows x64 wont boot when i have the UAD-1 inserted

[nuuuk]

My system is the following:
ASUS A8N-SLI premium
AMD64 x2 + 4800
Gforce 6600
Window x64

When i install the UAD-1 board in any PCI slot, my windows x64 wont boot. The computer keep restarting. Does anyone know why and how i can solve the problem.

Best regards
Nicklas Boesen

 

[Dan Duskin]

Move the UAD-1 card to a different slot... and if you can, make sure it's a regular PCI 32-bit 32MHz PCI slot. You may have to try several PCI slots... and it may be a good idea to uninstall your UAD-1 drivers first, power down, remove the card, power up, power down, put the card in a new slot, power up and re-install the drivers (make sure they are the latest).

 

[nuuuk]

I forgot to write that the computer is new so the card and drivers have never been installed. I have allready tried all PCI slots.

Best regards
Nicklas Boesen

 

[bulls hit]

Try installing the drivers first, then plug the card in

 

[jcat]

My system is the following:
ASUS A8N-SLI premium
AMD64 x2 + 4800
Gforce 6600
Window x64

When i install the UAD-1 board in any PCI slot, my windows x64 wont boot. The computer keep restarting. Does anyone know why and how i can solve the problem.

Best regards
Nicklas Boesen

There are no Windows x64 drivers fothe UAD-1!

#-o



Cheers,

jcat

 

[rimbaud234]

I don't understand why people try to get Windows 64 going for audio systems when there are likely to be driver issues (if they exist).
It's hard enough to get these systems working with Windows 32 bit software that the apps and cards were built for!
I've heard nothing but troubles.

 

[neil wilkes]

Also, x64 running 32 bit code is lower resolution than a 32 bit system running the same code.

I really wish that the whole x64 thing would just go away - it's not better for Audio, and will almost certainly be lower resolution.

 

[jcat]

Also, x64 running 32 bit code is lower resolution than a 32 bit system running the same code.

I really wish that the whole x64 thing would just go away - it's not better for Audio, and will almost certainly be lower resolution.

That won't effect the audio quality though, and it does bring memory enhancementst that will be essential over the next few years.

Theres always pros and cons, I think wishing it would all go away is a little OTT.



Cheers,

jcat

 

[stonefree]

Whether or not 64 bit drivers exist shouldn't affect whether Windwos boots AFAIK. It would just go into the \"New Hardware Found\" wizard. So it may be a deeper problem, or it just may be Windows being finnicky and needing the drivers beforehand, which it normally doesn't. Until 64 bit drivers are released we may never know.

 

[neil wilkes]

Also, x64 running 32 bit code is lower resolution than a 32 bit system running the same code.

I really wish that the whole x64 thing would just go away - it's not better for Audio, and will almost certainly be lower resolution.

That won't effect the audio quality though, and it does bring memory enhancementst that will be essential over the next few years.

Theres always pros and cons, I think wishing it would all go away is a little OTT.



Cheers,

jcat

According to Joe Bryant it will!

I quote

Win64 supports two application modes: 32-bit (for compatability), and 64-bit. If an app is compiled to run in 64-bit mode, it can't load 32-bit plugins or add-ons. Also, since there's no x87 FPU in 64-bit mode, all the floating point code must be reworked to run on the vector units. So for example, if a plugin has optimized assembly code (like most good native plugs), these have to be completely rewritten to work in 64-bit mode on the new floating point hardware! Some plugins may already have been written to use the vector units (like some synths and impulse 'verbs), so these would port more easily assuming the vector code is the only low-level assembly code.

As appealing as 64-bit mode is, the sonic benefits simply aren't there. In fact, the internal precision of the vector units is lower than the x87 FPU! The vector units can process 32- and 64-bit floats, but their internal resolution is fixed at the same precision. The x87 FPU on the other hand, always retains 80- or 160-bit internal prescion, and only drops the precision when results are saved to memory. Also, when 64-bit precision is used in the vector unit, performance is cut in half, so intensive 64-bit float code will be slower than 32-bit code.

The bottom line is that because of the availability of this more efficient, but lower resolution 32-bit float mode in Win64, some plugin vendors may opt to drop precision when supporting 64-bit application mode, and sound quality will be lower than what's currently available in the current 32-bit mode.

More can sometimes be less!

 

[jcat]

The bottom line is that because of the availability of this more efficient, but lower resolution 32-bit float mode in Win64, some plugin vendors may opt to drop precision when supporting 64-bit application mode, and sound quality will be lower than what's currently available in the current 32-bit mode.

So this won't effect UAD users then!

I can see from Joe's info that ther ar some some possible drawbacks, but som plugin vendors will choose not to drop precision for the very reasons above.

I still think the need to support more memory is a big one, which 64bit gives us. And I'm also not sure which if this applies to AMD and Intel or just Intel.

One this is for sure, processors are evelving all the time, we saw several generations of the 32bit technology, now I'm sure we'll see several generations of 64bit, with added features and enhancements that may change the situation that Joes is talking about.

I'm sure it will all work out in the end... :wink:



Xheers,

jcat

 

[Big Harpe]

This stuff happened when we went from 16 bit to 32 bit too. And it will happen again and again, when 64 bit goes to 128 bit, and 128 bit goes to 256 bit. It's called 'Planned Obsolescence'. It's the same reason why batteries die and light bulbs burn out.

They can make batteries that will last 100 times longer. They can make light bulbs that last nearly a lifetime. If they mass produced these products they would run themselves out of business.

Same thing goes for computers. Change, change, change... Make the stuff turn to crap in two years and make the end user buy a new one.

TV's, refrigerators and other appliances can't play this game. They would catch holy Hell from the public if they tried. Still, they do it with cheap parts so we need to replace the water pump on our washers and dishwashers one every 5-10 years

 

[Guest]

Planned Obsolescence'. It's the same reason why batteries die and light bulbs burn out

Spoken like a technocrat! at least that's what i hear.

YES planned obsolescence and false scarcity suck!!!!