This is a significant problem with dual-platform support. The only filesystem both platforms can fully access is FAT32. Unfortunately, FAT32 has size limitations and has other restrictions that limit its utility under OSX.
There's the 2/4 gig file size limitation. The specs allow for 4 gigs but many windows applications will choke on files larger than 2 gigs on a FAT32 filesystem so your effective limit on a FAT32 filesystem is 2 gigs. Second, there's the limited number of valid characters in filenames. You can use characters in HFS+ that you can't use in FAT32. (Heck, there are some versions of
windows that can't tolerate all of the characters allowed in the FAT32 spec, let alone all of the HFS+ characters.) Then there's the whole issue of HFS+ resource forks. A Mac folder on a FAT32 partition is not a pretty thing if you look at all of the hidden files.
If you absolutely must be able to use the drive on both platforms, FAT32 is currently the only choice you've got. While it has its limitations, it can be fully accessed by OSX, Windows, Linux, BSD, etc. Each system has much better native filesystems but they're pretty limited when it comes to support on other platforms. I've heard of an HFS+ program for Windows but you'd have to buy a license for every machine you use it on. Panther supposedly has read-only support for NTFS. Seems flaky, tho. I've heard several people complain about not being able to mount perfectly good NTFS partitions with Panther. And it's read-only.
It's long past time for "the industry" to get their act together and standardize filesystems.
