I might be mistaken but i think people saying this are talking about your primary hard drive, The one you install programs onto.

Flapperke;
The statement is related to the free space needed on the main OS drive (where Windows typically resides) and expresses the need to have adequate space for the temporary files created during system operation, etc.

Depending on your machine (feel free to show us your DXDIAG), where you install programs and what type of files you edit/produce, these needs can far EXCEED 100GIG.

Windows and programs LIKE the C: partition..even if you install them elsewhere, and point files elsewhere, the C: drive will continue to see heavy use due to scratch files, virtual memory/swap files and temporary files created during program operations.

The C:drive gets even more use in Windows 7 which eliminates some options of creating "Virtual Memory" residing on alternate drives.

Windows "rule of thumb" has always been to have no less than 20% of your %systemroot% drive free. For NLE programs like Cyberlink, there may be a need for much MORE that that. For example, the temporary file "overhead" on transcoding/rendering a file and producing it to YouTube or a DVD that is 100GIG may be 500GIG. Windows uses drive space (virtual memory) and Ram memory and swaps between the two during processing.

This is a LOT of HARDWARE talk, that goes far beyond the scope of "What does PD9 need", so suffice it to say...the MORE space you can free up on C:, the better! Manage temporary internet files and unneeded or discarded installation files often, to make sure the maximum amount of space is available. More space makes PD9 run better.

Thanks Fred,

but are you sure that I cannot deviate the working files of PD9 to another drive ?
Since even the swap file of Windows can do this...

thanks for you advice
Hugo

Flapperke;
Yes, you an point the working folder/export folder to another drive in PD9. You can also create a swapfile on alternate drives for Windows, but the internal processes in PD9 still use the swapfile on the masterdrive. In newer versions of windows you CAN NOT eliminate the swapfile on c: but can still manually set/create a swapfile/pagingfile on alternate drives for Programs INSTALLED on those drives.

Regardless of where they are installed, most programs and system software are designed to run their background processes against the %systemroot% drive as that is where most of the CODECS, etc. reside.

There are many hardware and software discussion forums that entertain this issue daily, and for each new OS. This discussion REALLY is outside of the limits of PD9 and it's use, so MY SUGGESTION would be that you free maximum space on the drive where Windows is installed, and that you plan for much MORE than 100GB if possible. All Windows programs (32 or 64 BIT), LOVE free space....HATE cramped quarters.

Thanks Fred.
My concerns in this discussion goes to 'speed'...
If I have my PD9 running from the C drive, which is itselve also used to 'host' all the temporar work file traffic, wouldn't the rendition times be influenced in the wrong direction ?
I mean, there was (is?) a time in video-editing where the advice was to keep programms on the root drive and all other stuff on dedicated other drives to speed up the editign/rendering process...

But if there is no way to change PD9's addiction to the C-drive : cleaning up is all I'm left to do :

I'm not into HD, only DVD. Guess a couple of dozens of Gb's will do.

:

Bye now,
Hugo

Quote: Flapperke;
Yes, you an point the working folder/export folder to another drive in PD9. You can also create a swapfile on alternate drives for Windows, but the internal processes in PD9 still use the swapfile on the masterdrive. .

So, is this down to the way PD9 has been written then? It does seem a bit limiting to be effectively tied to the drive where the os resides if its not actually necessary. It also goes against the practice of having your os on the C drive with your various data/games etc on other partitions and drives.I'm pretty sure the Adobe approach on scratch disks etc is to keep it away from the C: drive.

I'm a bit confused and I DO think this is fundamental to PD9, if there is some specific PD9 source material anyone can point me to, I would be grateful.

Flapperke;

I'm not into HD, only DVD. Guess a couple of dozens of Gb's will do.

I would never say that 24GB is adequate space for Windows EVER. You will see "thrashing" (the process of swapping RAM and virtual memory during program execution) that can sometimes create program failures and cause corruption. SPEED is impacted by the amount of thrashing that is required in a process. 100GIG is STILL not enough (in my humble opinion) as you share that space with MANY programs and processes in Windows.

EDIT:

Quote: excerpts.....So, is this down to the way PD9 has been written then? .....I'm a bit confused and I DO think this is fundamental to PD9,

I do NOT agree with _Angus that this is related to the way PD9 is designed..All Windows programs have adhered to the same set of development guidelines that use the %systemroot% as the main stack. Even Adobe products (that _Angus referred to), while allowing a "scratch disk" on alternate drives, revert to the %systemroot% for final processing.

Hi Fred,

Weird, my other PC system which had the premiere running, had a C drive of 20GB in total. Kept about 4-5 gigs free... My premiere stuff was 'scratched' to a another internal drive (500gb) .
Never had a problem with it...

: confusing it izzzz... :

Flapperke;
Yes, and my very first Network installation was a 20MB (yes Megabytes) "Corvus Constellation" Drive (with 14" platters) that ran the entire network for a Major Pediatric hospital's Biomedical Engineering and Construction department. (Link provided for Entertainment purposes only - - - > http://www.youtube.com/watch?v=5844LJhuNCg ) Time marches on!!

Quote: As the first consumer video editing software to support 64-bit Windows, PowerDirector is taking a lead in the field.December 7, 2010

OK, that is certainly a blatant plug

Please....folks....take this offline to a Hardware forum...really..not an issue that is PD9 related (again, in my humble opinion).

Quote: Flapperke;

EDIT:

Quote: excerpts.....So, is this down to the way PD9 has been written then? .....I'm a bit confused and I DO think this is fundamental to PD9,

I do NOT agree with _Angus that this is related to the way PD9 is designed.

Well, in fairness it was actually a question rather than a statement.

I'm just concerned with the requirements that PD9 has regarding what drive its installed on and how much space it needs for optimum performance. I would have thought this was a sensible place to try and find out - rather than to go chasing around hardware/os forums. Is there not an official statement from Cyberlink on this issue?

_Angus_;
Well, in the spirit of Fairness, I recognize that you were asking about a location for further information from Cyberlink:

...if there is some specific PD9 source material anyone can point me to, I would be grateful.

. There are some noticeable gaps in the details Cyberlink provides on "Requirements", but you might start HERE:
http://www.cyberlink.com/prog/support/cs/product-requirements.do?ProductId=4&prodId=4&prodVerId=848

Very few programs still REQUIRE that you install programs on the C: or the OS%systemroot% drive. The advent of large distributed resource environments, made this requirement difficult to justify or enforce. My statements were about what WINDOWS prefers. So much of what happens with programs is handled in the background by the OS... and how FAST it responds is very dependent on whether or not you follow their preferences. Windows likes Programs and swapfiles on the main OS drive and LOTS of free space for it's "temp" files.

Lots of problems that people think "belong" to Powerdirector, are actually the result of interaction between CODECS, Video Drivers and Hardware environments, unrelated to the program...Oh, it HAS BUGS..I have seen and experienced MANY, but not all things are the result of the guy programming the code.

Sorry if I misrepresented (or misconstrued) your interrogative.

FB

Quote: _Angus_;
Well, in the spirit of Fairness, I recognize that you were asking about a location for further information from Cyberlink:

...if there is some specific PD9 source material anyone can point me to, I would be grateful.

. There are some noticeable gaps in the details Cyberlink provides on "Requirements", but you might start HERE:
http://www.cyberlink.com/prog/support/cs/product-requirements.do?ProductId=4&prodId=4&prodVerId=848


Sorry if I misrepresented (or misconstrued) your interrogative.

FB

No problem - thank you for your responses.

Unfortunately,

"10 GB (20 GB recommended) for DVD production"

is about as helpful as it gets (which from what you say is a massive underestimate anyway.)

Its a shame Cyberlink don't offer some guidance on the issue we've been discussing of which drive/partition PowerDirector ought to be using.