Avid XP with Athlon64

C

Carlos_E._Martinez

Well-known member
Is there anyone running Avid with an Athlon64 based CPU?

After having a crash on my Gigabyte 7N400 Pro2, probably due to heat on CPU, I wanted to the Athlon64 path until I get an advice on a reliable mobo/Pentium combo.

What I bought was an Asus K8N with AMD 64 3000+ cpu, but I am having as hard time qwith time and can't seem to make Avid work with it.

My guess is it might be a driverconflict of some kind, and I intend to take the stuff back to the shop tomorrow. But should I get instead?
 
Tell me exactly what your problem is with AVID, maybe I can help you. I have (A64 3200+) mine running on Xpress Pro HD just fine...
 
jazzx said:
Tell me exactly what your problem is with AVID, maybe I can help you. I have (A64 3200+) mine running on Xpress Pro HD just fine...
Click to expand...

Which is your mobo?

What happens is this: after installing the program, I go and recall the external files from a documentary I did, which it is on another HD. They never get there: the sand clock starts on and you are stuck. Only a reset can get you out of it.

I did the same procedure on my wife's computer, which is an old Asus with AMX XP 1300 and same memory: the program opens the files and assembles them on the timeline.

Believe me I repeated this procedure several times, to see if I was doing something wrong.
 
I have the K8N-E Deluxe m/b. The issue you're describing looks more like a hard disk situation, what is your disk, DVD, IDE, sata config?
 
jazzx said:
I have the K8N-E Deluxe m/b. The issue you're describing looks more like a hard disk situation, what is your disk, DVD, IDE, sata config?
Click to expand...

My board is the plain Asus K8N: perhaps there's something better in the E Deluxe version.

It would be great if you could elaborate a bit more on what might be the problem on my HD situation. What should I look for?

The HD I am using as "c" for these tests, before I do the final installation, had nothing on it and was NTFS formatted. In fact: all my HDs are NTFS.

The parallel test I did, using the Avid video files as "d" HD on this setup and my wife's, seems to be simple enough. As I said, the Avid installation on my wife's finds the files and assembles the timeline. The other system fails to do that.

Once I tried four HDs d, e and f on the Sempron 64: same as they were on my original machine. The Avid Projects directory should have guided them to find everything, and it failed to find the files.

BTW: XP's disk manager shows all HDs as being healthy.
 
Last edited:
Are you using the system disk as a capture\video disk? Or is it a different one?
 
jazzx said:
Are you using the system disk as a capture\video disk? Or is it a different one?
Click to expand...

No, the present system disk (or the former "c" disk where the original info was in) is not used for capture or video store.
 
No what I'm saying is, do you have more than one physical disk on your machine or is it just one for everything?
 
jazzx said:
No what I'm saying is, do you have more than one physical disk on your machine or is it just one for everything?
Click to expand...

No, I have several disks on my machine. For that job I am trying to retrieve now I used four HDs: one for the system and two others for holding the original captured files and render information. The fourth was not used.
 
A happy end for this story and shame on me for being so scared so as not to do what I had to.

The problem was BIOS update. After I did that, almost as a last thing before going tomorrow to return mobo and CPU things went smoothly. I had downloaded the BIOS file, then copying it onto a floppy disc.

The scary state I mention above is because dealing with BIOS with floppies seems quite dangerous to me, and I didn't think that update was so back behind. Apparently it was.

Now Avid sees all and assembles the edit quite well, so I can start working again on refining it.

Several lessons to come from this:

1) First thing to do on a new mobo: update BIOS. No matter how new the mobo is.

2) Use Sysprep to wipe the drivers from your old mobo and XP will just ask for the new ones when you connect to the new mobo. Apparently that is the way to keep all your C organization intact.

3) Look for a way to save and protect your editings, and if possible keep all information for same job on same disc.
 
Last edited:
You must log in or register to reply here.
Back
Top