I think if you can read the code, you'd be set.
As was mentioned, the first 100 bytes are loaded in a fraction of a second. Within that fraction of a second, a reliable value for getBytesTotal() does not exist. So what the above code does is ignore getBytesTotal() altogether until getBytesLoaded() is greater than 100.
This has nothing to do with getBytesTotal() actually being equal to 100, as you can see in the code- so what I was saying (and what I was hoping would be plain as day by just reading the code) was that you're not preloading just 1/10th of a kilobyte. Rather, in the time it takes to load 1/10th of a kilobyte, you really have no idea how much you're trying to load in total.
Now I have two problems with the code. First, would the getBytesTotal() ever be so unreliable that it would be less than or equal to getBytesLoaded()? If not, then the problem can be ignored altogether. Otherwise, then the code is somewhat necessary to keep you from loading a movie far before it's ready. Second, the code can't be used if getBytesTotal() actually is less than 100 bytes.. but that's pretty unlikely and, as was previously mentioned, there's no need for a preloader in that case.
Hopefully the code makes more sense to you now and is less "futile". Liam Morley
lmorley@gdc.wpi.edu
"light the deep, and bring silence to the world.
light the world, and bring depth to the silence."