| Printable Version of Topic
Click here to view this topic in its original format |
| Unofficial VirtualDub Support Forums > Testing / Bug Reports > Incorrect Free Disk Space? |
| Posted by: fccHandler Feb 25 2003, 07:12 AM |
| I have a 15GB drive devoted exclusively to capture, but VirtualDub 1.5.1 always reports 2047.7MB free while I'm capturing. The "Time left" display is likewise incorrect, and fluctuates around what might be expected if I only had 2GB free. (I haven't seen what happens if I let the actual free space drop below 2GB yet.) Capture still proceeds unhindered (well over 4GB so far), so I'm not too concerned about it; nevertheless this behavior is different from 1.4.13. What changed? I'm on Win98SE, FAT32, using "multisegment" capture. If you want more info, ask away. |
| Posted by: phaeron Feb 25 2003, 08:51 AM |
| Debugging this is a bit of a problem for me, since I no longer have Windows 95/98 installed anywhere other than VirtualPC, which doesn't support video capture. The reason for the change in 1.5 is that the old free disk space code had two problems: it didn't understand Unicode filenames, and it didn't work with NTFS mounted drives or quotas. However, the new code is bugged too and the code that is supposed to call GetDiskFreeSpaceEx() doesn't work -- GetDiskFreeSpace() is used instead. Apparently, under Windows 2000, the latter can report free disk space >4GB, but under 98 it is limited to 2GB. Below 2GB it should report the proper amount of free disk space. The fix in the source code is embarrasingly simple: change sbInited to !sbInited in system/source/filesys.cpp. |
| Posted by: fccHandler Feb 25 2003, 06:20 PM |
| Thanks for your help, it works now! |
| Posted by: jcsston Mar 1 2003, 07:23 AM |
| I just wanted to add that under Win98Se it reports around 4GB free. But in WinXP the correct 60GB amount is reported. |
| Posted by: profound_infanity Mar 10 2003, 04:12 PM |
| i also face the same problem under win98 se ,since i am a new user so i dont have the source code nor does know how to compile it .is there i easire way to slove the problem?? |
| Posted by: fccHandler Mar 10 2003, 05:45 PM |
| http://home.attbi.com/~blade66 of VirtualDub has the fix which phaeron described. |
| Posted by: Randolph Carter Apr 25 2003, 08:21 AM |
| Dear FCCHANDLER, Thank you for your help! BUT what shall we oldfashione Windows98(SE) Users do for the future? For my part I will not upgrade because my soundequipment has no drivers for XP ... And IŽd like to build a P4 version of 1.5.1 including the "change sbInited to !sbInited in system/source/filesys.cpp" patch ... What prog do you use to compile the source? THX for your help!!! randolph |
| Posted by: Randolph Carter Apr 25 2003, 09:22 AM |
| @ Phaeron: Thank you for your help, but just one Question: I have taken a look at the 1.5.1. SourceCode, but I canŽt finde the "sbInited" which should be changed to"!sbInited" in system/source/filesys.cpp in the sourcecode folder... Can you please give me a hint, where to look? best regards from vienna - austria to all VDubbers... |
| Posted by: fccHandler Apr 25 2003, 03:34 PM | ||||
I expect that future versions of VirtualDub will have the bug fixed.
I'm using Visual C++ 6, SP 5, with the include files from the latest Platform SDK. I can't build the P4 version because I don't have the necessary Intel compiler. The problem variable in filesys.cpp is actually called "sbChecked." |