125 gigs free = out of space

[Husky]

This happened with 2 different programs which makes me now believe it's an XP
problem.
specifically examples: the ATI AIW 9800 creates VCR files to record from TV.
Not real sure what the base format of these are maybe some sort of AIW modified
mpg format. neither here nor there...
created both an 18.5 meg from a commercial and a 200+ meg from a half hour TV
show.
It has the option to save/convert to mpg.
the 18.5 meg one brings up the 'not enough drive space' error. the 200+ meg one
goes right along not a glitch.

2nd example. old irfanview from win98 days needed upgraded. didn't support
newest video formats. ie:mpg-2.

also grabbed the plugin's.exe from irfanview. installed iv no problem, tried to
install the plugin's and once again got the out of drive space error.

The logical assumption is that both AIW and irfanview didn't do their homework
and missed an error checking step. And hopefully these are the only 2 programs
this affects.

Well how many programs have you attempted to install under XP pro and had them
report back not enough drive space on a 126 gig free of 160 gigs drive ?

Or is this something else ?
more pix @ http://members.toast.net/cbminfo/index.html

 

[Jeffrey Struyk - MVP]

This happened with 2 different programs which makes me now believe it's an XP
problem.
specifically examples: the ATI AIW 9800 creates VCR files to record from TV.
Not real sure what the base format of these are maybe some sort of AIW modified
mpg format. neither here nor there...
created both an 18.5 meg from a commercial and a 200+ meg from a half hour TV
show.
It has the option to save/convert to mpg.
the 18.5 meg one brings up the 'not enough drive space' error. the 200+ meg one
goes right along not a glitch.

2nd example. old irfanview from win98 days needed upgraded. didn't support
newest video formats. ie:mpg-2.

also grabbed the plugin's.exe from irfanview. installed iv no problem, tried to
install the plugin's and once again got the out of drive space error.

The logical assumption is that both AIW and irfanview didn't do their homework
and missed an error checking step. And hopefully these are the only 2 programs
this affects.

Well how many programs have you attempted to install under XP pro and had them
report back not enough drive space on a 126 gig free of 160 gigs drive ?

Or is this something else ?
more pix @ http://members.toast.net/cbminfo/index.html

I ran into similar problems when I was capturing VCR video digitally.
I was filling up my hard drive and could not seem to free it up. I
traced it down to the Norton Protected Recycle Bin.

 

[Husky]

On Sun, 25 Jul 2004 09:00:11 -0500, Jeffrey Struyk - MVP <MVP> wrote:


I've heard nothing good about Norton. It causes more problems than it fixes.
Can't run program x if you have the virus running, can't install x if virus
checker is on, etc.. Don't have the Norton protected trash on. XP pro protects
things way beyond anything Norton ever considered.
Good guess, but I'm sure that's not the problem.
ie: I did an info on that specific 18.5 meg mpg from irfanview and it's size
was -183367832 kb.
It's now gone, I renamed it and extracted the portions I wanted from it.

I ran into similar problems when I was capturing VCR video digitally.
I was filling up my hard drive and could not seem to free it up. I
traced it down to the Norton Protected Recycle Bin.

more pix @ http://members.toast.net/cbminfo/index.html

 

[D.Currie]

This happened with 2 different programs which makes me now believe it's an XP
problem.
specifically examples: the ATI AIW 9800 creates VCR files to record from TV.
Not real sure what the base format of these are maybe some sort of AIW modified
mpg format. neither here nor there...
created both an 18.5 meg from a commercial and a 200+ meg from a half hour TV
show.
It has the option to save/convert to mpg.
the 18.5 meg one brings up the 'not enough drive space' error. the 200+ meg one
goes right along not a glitch.

2nd example. old irfanview from win98 days needed upgraded. didn't support
newest video formats. ie:mpg-2.

also grabbed the plugin's.exe from irfanview. installed iv no problem, tried to
install the plugin's and once again got the out of drive space error.

The logical assumption is that both AIW and irfanview didn't do their homework
and missed an error checking step. And hopefully these are the only 2 programs
this affects.

Well how many programs have you attempted to install under XP pro and had them
report back not enough drive space on a 126 gig free of 160 gigs drive ?

Or is this something else ?
more pix @ http://members.toast.net/cbminfo/index.html

I haven't had it happen with drives that large, but I've seen it happen a
number of times with older programs that didn't understand larger drives and
would miscalculate the free space somehow. Back then, the programs, when
checking drive space, would ignore amounts above whatever limit it believed
to be possible. So, if it thought 8 gig was the limit, it would ignore
anything above that. If you had 7.9 gig of a 32 gig drive filled, it would
only see the .1 of free space. But if you filled another .2 gigs space, it
would see the next increment, so it would recognize 7.9 free.

The fact that you've got 2 programs that have problems, but others that
don't, would indicate that there's some problem with the way those programs
"see" larger drives, rather than a problem with XP or with the drive itself.
And considering you're right at that point that used to be the HD space
limit is another clue. I wouldn't be surprised if those programs started
working correctly after you fill a couple more gigs of space.

 

[Husky]

them report back not enough drive space on a 126 gig free of 160 gigs drive ?

And considering you're right at that point that used to be the HD space
limit is another clue. I wouldn't be surprised if those programs started
working correctly after you fill a couple more gigs of space.

Huh ? Limit ? 126 gigs free on a 160 gig drive. It's nowhere near filling the
limit. I've only used 34 gigs.
And most of that's cause I haven't figured out how to eliminate 90% of the user
accounts and directories that XP created automatically and promptly locked from
deletion. I stick something one place and it shows up somewhere else.
Then have to keep installing till it lands in the right place.
I probably have 15 shortcuts scattered everywhere to every program.

more pix @ http://members.toast.net/cbminfo/index.html

 

[D.Currie]

Huh ? Limit ? 126 gigs free on a 160 gig drive. It's nowhere near filling the
limit. I've only used 34 gigs.
And most of that's cause I haven't figured out how to eliminate 90% of the user
accounts and directories that XP created automatically and promptly locked from
deletion. I stick something one place and it shows up somewhere else.
Then have to keep installing till it lands in the right place.
I probably have 15 shortcuts scattered everywhere to every program.

more pix @ http://members.toast.net/cbminfo/index.html

I don't think you're getting the concept. If the program can only understand
a drive of a certain size (or more accurately, free space of a certain
size), if you have more space than that, it doesn't see it all because
according to its calculations, that amount of free space isn't possible. So
it ignores the amount of space it can't understand and it sees the free
space that makes sense to it. So if the program only understands a drive
with free space of, for example, 125 gigs, and you have 126 gigs free, it
wouldn't see your first 125 gigs of free space, it would just ignore it and
it would just see one gig of free space. In this example, if you filled
another couple of gigs, you'd be under the amount the drive could
understand, so instead of seeing one gig free, it would see 124 gigs free.

When I said you were close to the drive limit, I was referring to the fact
that until recently, the upper limit for drives was less than your 160 Gig
and it hasn't been that long that drives over 100 gig were a rarity. So it's
possible that your programs are doing free space calculations based on
whatever upper limit or whatever drive geometry it understands. So when you
have less free space, it may be able to understand it better and install
properly.

I've seen this sort of miscalculations dating way back. Every time there's a
new partition size allowed or a new hard drive limit broken, there are
programs that can't understand the new sizes. This may not, ultimately, be
what your problem is, but based on the symptoms, it's a good guess.

 

[Husky]

Well whatever it was, it's gone now. I just taped the same commercial and got
15 megs vs 18. also installed the irfanview plugins.
the 15 megger exported fine also. Can't explain it.
I hate these erratic errors. they're worse than a real problem.
probably happen again a month from now and I'll still have no idea what caused
it and it'll probably be 2 different programs that go out.

I don't think you're getting the concept. If the program can only understand
a drive of a certain size (or more accurately, free space of a certain
size), if you have more space than that, it doesn't see it all because
according to its calculations, that amount of free space isn't possible. So
it ignores the amount of space it can't understand and it sees the free
space that makes sense to it. So if the program only understands a drive
with free space of, for example, 125 gigs, and you have 126 gigs free, it
wouldn't see your first 125 gigs of free space, it would just ignore it and
it would just see one gig of free space. In this example, if you filled
another couple of gigs, you'd be under the amount the drive could
understand, so instead of seeing one gig free, it would see 124 gigs free.

When I said you were close to the drive limit, I was referring to the fact
that until recently, the upper limit for drives was less than your 160 Gig
and it hasn't been that long that drives over 100 gig were a rarity. So it's
possible that your programs are doing free space calculations based on
whatever upper limit or whatever drive geometry it understands. So when you
have less free space, it may be able to understand it better and install
properly.

I've seen this sort of miscalculations dating way back. Every time there's a
new partition size allowed or a new hard drive limit broken, there are
programs that can't understand the new sizes. This may not, ultimately, be
what your problem is, but based on the symptoms, it's a good guess.

more pix @ http://members.toast.net/cbminfo/index.html

 

[D.Currie]

Well, that's good. Maybe it won't come back and you won't need to know why.

 

[Joe]

I had a similar problem and found that the program had a scratch disk
setting that was set at 100mb by default. I know this is an issue with Adobe
PhotoShop, so I would just check to see if your program has a scratch disk.