I'm on Win 7 and the grass folder with edius 6 is under program files X64 - I guess this normal ? my system has slowed to a crawl so I guess something else is going on....
john
Edius finally opened after waiting for over an hour....gurss I have some serious sytem issues !! thanks for your help - guess i'll take her in.....
john
EDIUS X WG with BM Mini Monitor 4k and BM Mini Recorder, Gigabyte X299 UD4 Pro, Intel Core i9 9960X 16 Core, 32 Threads @ 4.3Ghz, Corsair Water Cooling, Gigabyte RTX-2070 Super 3X 8GB Video Card, Samsung 860 Pro 512GB SSD for System, 8TB Samsung Raid0 SSD for Video, 2 Pioneer BDR-209 Blu-ray/DVD burners, Hotswap Bay for 3.5" Sata and 2.5" SSD, Phanteks Enthoo Pro XL Tower, Corsair 32GB DDR4 Ram, Win10 Pro
Edius should be installed in "Program Files (x86)" (x86 = 32bit programs)
all 64 bit programs are installed in "Program Files"
there is no x64 folder in Win7
Actually, there is NO distinction to Windows. You can put a 64 bits program in "Program Files (x86)" or a 32 bits program in "Program Files" - and it will still run. The program attributes (whether 32 bits or 64 bits) are embedded in the EXE file itself.
TingSern
--------------------------------------
Edius 10 WG, Lenovo P72 workstation laptop, 64GB RAM, Xeon CPU, Windows 11 Pro (64 bits), 2 x 2TB Samsung M2.NVME and 1 x 4TB Samsung SSD internal. Panasonic UX180 camera, Blackmagic 4K Pocket Cinema
EDIUS X WG with BM Mini Monitor 4k and BM Mini Recorder, Gigabyte X299 UD4 Pro, Intel Core i9 9960X 16 Core, 32 Threads @ 4.3Ghz, Corsair Water Cooling, Gigabyte RTX-2070 Super 3X 8GB Video Card, Samsung 860 Pro 512GB SSD for System, 8TB Samsung Raid0 SSD for Video, 2 Pioneer BDR-209 Blu-ray/DVD burners, Hotswap Bay for 3.5" Sata and 2.5" SSD, Phanteks Enthoo Pro XL Tower, Corsair 32GB DDR4 Ram, Win10 Pro
If the installer is well-behaved and queries the OS for the "Program Files" location then it'll get the proper Program Files for 64-bit or Program Files (x86) for 32-bit applications.
Some older/ill-behaved installers have hardcoded paths, which is bad. You usually don't see it much for Program Files, but it happens semi-often for the user profile - trying to write directly to C:\Documents and Settings for example.
Comment