Hello,
I have an NTFS volume on an NTFS drive with 30gig free space. VS8 won't allow me to create a 2gig file on this volume and reports 'Insufficient Disk Space' VS 7 works fine with this volume as there is actually plenty of space.
I tried to apply their latest patches and it didn't help but did introduce the audio sync problem that's been reported all over the place.
Anyone have a solution to this problem?
Thanks!!
P.S. I've owned VS since version 5 and this is the worst version I've ever used. It's a horrible product!!
VS 8 Insufficient Disk Space on NTFS drive
Moderator: Ken Berry
-
Trevor Andrew
-
bm
My working folder is located in the same place as my project on the NTFS volumne. This is the same place VS 7's project is located which works.
I tried to locate the working folder to a non-NTFS drive with ample space and I get the same error when trying to create a file either in the 'Save trimmed video' optino or 'Create file' in the Share section.
I think VS 8 can't handle NTFS volumes.
Thanks
I tried to locate the working folder to a non-NTFS drive with ample space and I get the same error when trying to create a file either in the 'Save trimmed video' optino or 'Create file' in the Share section.
I think VS 8 can't handle NTFS volumes.
Thanks
-
maddrummer3301
- Posts: 2507
- Joined: Fri Dec 10, 2004 10:24 pm
- Location: US
Hi,
Under the Preferences tab (F6), make sure the Temp folder is
pointing to a NTFS partition (of good size).
It's the last tab on the right. UnCheck the default HOME folder
and assign a folder on a good size NTFS partition.
The default points to the users home directory on the system drive.
Sometimes the system drive is pretty full or formated as FAT32
which has limitations.
The program needs the temp space to build projects etc.
So make all your pointers point to NTFS partitions large enough
for video editing.
Hope this helps,
MD
Under the Preferences tab (F6), make sure the Temp folder is
pointing to a NTFS partition (of good size).
It's the last tab on the right. UnCheck the default HOME folder
and assign a folder on a good size NTFS partition.
The default points to the users home directory on the system drive.
Sometimes the system drive is pretty full or formated as FAT32
which has limitations.
The program needs the temp space to build projects etc.
So make all your pointers point to NTFS partitions large enough
for video editing.
Hope this helps,
MD
-
Chaotrix
Hello,
I'm having the same problem. I performed the actions MD suggested even though all my drives are NTFS and had more than enough room. The first time I had a problem I was creating a file about 10 gigs in size. I got the "Insufficient disk space" error. I cut the project in half. V8 created a 5 gig file and promptly crashed. Trying to look at the file caused Windows Explorer to crash. Very strange. And repeatable. Has anyone successfully created a file over the 4 gig limit with V8?
Philip
I'm having the same problem. I performed the actions MD suggested even though all my drives are NTFS and had more than enough room. The first time I had a problem I was creating a file about 10 gigs in size. I got the "Insufficient disk space" error. I cut the project in half. V8 created a 5 gig file and promptly crashed. Trying to look at the file caused Windows Explorer to crash. Very strange. And repeatable. Has anyone successfully created a file over the 4 gig limit with V8?
Philip
-
maddrummer3301
- Posts: 2507
- Joined: Fri Dec 10, 2004 10:24 pm
- Location: US
Hi,
Some other info may possibly help:
You usually need at least double the space then the project is going to take.
Ulead always suggests to keep the temp directories clean.
Maybe you need to "ScanDisk" your drives for errors.
Probably have to reboot to do that. You can mark all of them to be
checked upon re-starting.
You said the system has crashed, that can leave a drive partially corrupted.
After checking the drives look for any folders called FILE0000.
Those are the files (if any) that are lost and dumped into that directory.
Hope this helps,
MD
Some other info may possibly help:
You usually need at least double the space then the project is going to take.
Ulead always suggests to keep the temp directories clean.
Maybe you need to "ScanDisk" your drives for errors.
Probably have to reboot to do that. You can mark all of them to be
checked upon re-starting.
You said the system has crashed, that can leave a drive partially corrupted.
After checking the drives look for any folders called FILE0000.
Those are the files (if any) that are lost and dumped into that directory.
Hope this helps,
MD
To answer the question posed by Chaotrix:
Yes, indeed. I would have to say (guess) that most people are finding VS8 as useful as VS7. People who have problems with it, talk up on the forum and so appear to be more numerous. Nothing wrong with that.
I've been using VS8 since the day it became available (boxed version) on, first, an Athlon 1.3 with 500 RAM, and now a P4 3G with 1GB RAM. The only difference between them was speed. I've had no crashes, no problems with "disk space" limitations, etc.
But I have had "no disk space" warnings, and at those time I've discovered that my working folder has filled up the hard drive. I'm usually working with more than one project at a time, and 120GB doesn't go that far.
There are no occasions when the disk-space warning told me falsely.
Keith
Yes, indeed. I would have to say (guess) that most people are finding VS8 as useful as VS7. People who have problems with it, talk up on the forum and so appear to be more numerous. Nothing wrong with that.
I've been using VS8 since the day it became available (boxed version) on, first, an Athlon 1.3 with 500 RAM, and now a P4 3G with 1GB RAM. The only difference between them was speed. I've had no crashes, no problems with "disk space" limitations, etc.
But I have had "no disk space" warnings, and at those time I've discovered that my working folder has filled up the hard drive. I'm usually working with more than one project at a time, and 120GB doesn't go that far.
There are no occasions when the disk-space warning told me falsely.
Keith
-
bm
Hello,
As I mentioned in both of my posts, I have plenty of space on my ntfs drives, 30 gig of freespace and I'm only trying to create a file of 2gig. I also pointed out that I have the temp folder pointed to the drive with the 30 gig of free space as well as other drives that also have plenty of free space.
I'm glad some people are using the product without any problems but the problems listed in this forum are REAL and aren't dreamed up by people that don't know how to use a computer or the product.
I won't go into the other problems I've encountered but I can use VS7 and this problem doesn't exist. I use VS8 and the problem does.
As I mentioned in both of my posts, I have plenty of space on my ntfs drives, 30 gig of freespace and I'm only trying to create a file of 2gig. I also pointed out that I have the temp folder pointed to the drive with the 30 gig of free space as well as other drives that also have plenty of free space.
I'm glad some people are using the product without any problems but the problems listed in this forum are REAL and aren't dreamed up by people that don't know how to use a computer or the product.
I won't go into the other problems I've encountered but I can use VS7 and this problem doesn't exist. I use VS8 and the problem does.
-
video_flux
BM is right. This happens to me with 60G of free space. I captured a 20Gig file
-
rcjsr
-
PeterMilliken
- Posts: 264
- Joined: Sun Dec 12, 2004 9:03 pm
- Location: Sydney, Australia
Perhaps give some thought to the fact that there are many of us using VS8 and we do not have space problems such as reported in this thread - not many people here with the problem are there? 
So the problem becomes extremely difficult to help diagnose (I have a 40G main drive that I have VS8 installed on and an 80G secondary that is purely devoted to video files and projects and never experienced a problem such as described).
I have noticed from others posts to this forum that quite frequently supposed VS8 "problems" have been in actual fact problems with compatibility with other products. Perhaps you could investigate the problem from that perspective? My suggestion would be to start with a "cleanskin" system i.e. re-image your harddrive to include *only* your OS (WIndows XP?) and VS8 - nothing else, no Nero no nothing. Then try performing your capture and let us know how it goes (P.S. This is also an ideal point at which to "snapshot" your system - bare minimum to which you can return at any stage that you find "weird" problems that nobody else experiences).
Just a suggestion anyway - whilst we don't doubt your antecedants, knowledge or ability with a keyboard you can only expect help when people have experienced (and solved) similar problems - it doesn't look like this is a case in this instance, so perhaps we can broaden the net?
Goodluck and please let us know how you go,
Peter
So the problem becomes extremely difficult to help diagnose (I have a 40G main drive that I have VS8 installed on and an 80G secondary that is purely devoted to video files and projects and never experienced a problem such as described).
I have noticed from others posts to this forum that quite frequently supposed VS8 "problems" have been in actual fact problems with compatibility with other products. Perhaps you could investigate the problem from that perspective? My suggestion would be to start with a "cleanskin" system i.e. re-image your harddrive to include *only* your OS (WIndows XP?) and VS8 - nothing else, no Nero no nothing. Then try performing your capture and let us know how it goes (P.S. This is also an ideal point at which to "snapshot" your system - bare minimum to which you can return at any stage that you find "weird" problems that nobody else experiences
).Just a suggestion anyway - whilst we don't doubt your antecedants, knowledge or ability with a keyboard you can only expect help when people have experienced (and solved) similar problems - it doesn't look like this is a case in this instance, so perhaps we can broaden the net?
Goodluck and please let us know how you go,
Peter
-
Chaotrix
Peter,
Of the eight people who have posted messages to this thread, four of them have had the "disk space error" problem. That's 50%. Your comment "not many people here with the problem are there?" was not appreciated. How many people have actually tried to create a video file that was larger than the 4gig FAT limit on an NTFS drive?
Your suggestion that we "cleanskin" our systems because of "compatibility" problems only begs the question. It's still Ulead's responsibility to put out a compatible product. Saying "I have noticed from others posts to this forum that quite frequently supposed VS8 "problems" have been in actual fact problems with compatibility with other products" makes you sound like a Ulead shill.
VS8 has a host of problems. This disk space issue is only one of them.
Philip
Of the eight people who have posted messages to this thread, four of them have had the "disk space error" problem. That's 50%. Your comment "not many people here with the problem are there?" was not appreciated. How many people have actually tried to create a video file that was larger than the 4gig FAT limit on an NTFS drive?
Your suggestion that we "cleanskin" our systems because of "compatibility" problems only begs the question. It's still Ulead's responsibility to put out a compatible product. Saying "I have noticed from others posts to this forum that quite frequently supposed VS8 "problems" have been in actual fact problems with compatibility with other products" makes you sound like a Ulead shill.
VS8 has a host of problems. This disk space issue is only one of them.
Philip
-
PeterMilliken
- Posts: 264
- Joined: Sun Dec 12, 2004 9:03 pm
- Location: Sydney, Australia
Philip,
There was no intent to cause disturbance or offend anyone participating in this thread, only a desire to offer some (possibly meaningless?) advice in helping to resolve the problem. The messages in this thread display a great deal of frustration - which I can appreciate and sympathise with whole heartedly. I could just as easily ignore the problems as the problem doesn't affect me
My advise was offered based purely on the fact that other users had resolved "unusual" problems in the past by determining that some other product that they had installed seemed to be affecting the behaviour of VS8.
As for your 50% figure, I looked at the membership figures for the forum, there are currently 2863 registered members to the list - 4 of whom have complained about this problem in this thread (I didn't search for other threads complaining of the same problem). So perhaps your figures might be slightly off base? If I was ULead selling a $100 product and less than 0.14% of my customer base complained of a particular problem then I might be tempted to fix problems which had a higher complaint ratio first - especially since the statistics argued that it might not be a problem with "my" product at all!
You have a perfect right to ignore any and all advise I post on this thread - feel free to deal with the frustration of having paid for something that won't do what you want in any way you feel up to it
Goodluck,
Peter
There was no intent to cause disturbance or offend anyone participating in this thread, only a desire to offer some (possibly meaningless?) advice in helping to resolve the problem. The messages in this thread display a great deal of frustration - which I can appreciate and sympathise with whole heartedly. I could just as easily ignore the problems as the problem doesn't affect me
My advise was offered based purely on the fact that other users had resolved "unusual" problems in the past by determining that some other product that they had installed seemed to be affecting the behaviour of VS8.
As for your 50% figure, I looked at the membership figures for the forum, there are currently 2863 registered members to the list - 4 of whom have complained about this problem in this thread (I didn't search for other threads complaining of the same problem). So perhaps your figures might be slightly off base? If I was ULead selling a $100 product and less than 0.14% of my customer base complained of a particular problem then I might be tempted to fix problems which had a higher complaint ratio first - especially since the statistics argued that it might not be a problem with "my" product at all!
You have a perfect right to ignore any and all advise I post on this thread - feel free to deal with the frustration of having paid for something that won't do what you want in any way you feel up to it
Goodluck,
Peter
-
Ohotnik
Hi Philip,
I am one of users of UVS-8, so far have made 15 DVD's, smallest 1.5hrs. and longest 2:04. Using Canopus ADVC-100 I capture non-stop one of these movies - one at a time with no problem. After project is completed, rendered and burned to DVD ( total some times up to 35-40 GB ) I remove it from hard disc all that belongs to it and start new project.
My hard disc is 80GB, 65-of wich is allways available, file system is NTFS, so far-thanks God-no problem to fit all the DV-AVI data from Canopus.
Switched from UVS-6 to UVS-8, had to un-instal UVS-6 completely before installing UVS-8.
Ciril.
I am one of users of UVS-8, so far have made 15 DVD's, smallest 1.5hrs. and longest 2:04. Using Canopus ADVC-100 I capture non-stop one of these movies - one at a time with no problem. After project is completed, rendered and burned to DVD ( total some times up to 35-40 GB ) I remove it from hard disc all that belongs to it and start new project.
My hard disc is 80GB, 65-of wich is allways available, file system is NTFS, so far-thanks God-no problem to fit all the DV-AVI data from Canopus.
Switched from UVS-6 to UVS-8, had to un-instal UVS-6 completely before installing UVS-8.
Ciril.
-
Ohotnik
Hi Philip,
I am one of users of UVS-8, so far have made 15 DVD's, smallest 1.5hrs. and longest 2:04. Using Canopus ADVC-100 I capture non-stop one of these movies - one at a time with no problem. After project is completed, rendered and burned to DVD ( total some times up to 35-40 GB ) I remove it from hard disc all that belongs to it and start new project.
My hard disc is 80GB, 65-of wich is allways available, file system is NTFS, so far-thanks God-no problem to fit all the DV-AVI data from Canopus.
Switched from UVS-6 to UVS-8, had to un-instal UVS-6 completely before installing UVS-8.
Ciril.
I am one of users of UVS-8, so far have made 15 DVD's, smallest 1.5hrs. and longest 2:04. Using Canopus ADVC-100 I capture non-stop one of these movies - one at a time with no problem. After project is completed, rendered and burned to DVD ( total some times up to 35-40 GB ) I remove it from hard disc all that belongs to it and start new project.
My hard disc is 80GB, 65-of wich is allways available, file system is NTFS, so far-thanks God-no problem to fit all the DV-AVI data from Canopus.
Switched from UVS-6 to UVS-8, had to un-instal UVS-6 completely before installing UVS-8.
Ciril.