can t write vista b2 workgroup shares fat 32 xp

I've installed Windows Vista Beta 2 in a 5-computer network. 2 of the other machines are using the NTFS file system and 2 are formatted as FAT 32 file system. The machines (an XP SP1 and W2K) with NTFS can access, read, & write with no problems to shared drives on the Vista machine; the 2 machines, both XP SP1, formatted as FAT 32 can access, read, & copy but not write to the Vista shared drives. Could this be by design or a bug to be worked out in the Beta system? Has anyone noticed this? I've tried unchecking "Use Sharing Wizard" in Folder Options/View, but this had no effect.

Vista does not support Fat partitions
"CathLB" wrote:

I've installed Windows Vista Beta 2 in a 5-computer network. 2 of the other machines are using the NTFS file system and 2 are formatted as FAT 32 file system. The machines (an XP SP1 and W2K) with NTFS can access, read, & write with no problems to shared drives on the Vista machine; the 2 machines, both XP SP1, formatted as FAT 32 can access, read, & copy but not write to the Vista shared drives. Could this be by design or a bug to be worked out in the Beta system? Has anyone noticed this? I've tried unchecking "Use Sharing Wizard" in Folder Options/View, but this had no effect.

Thanks for responding. To clarify: my FAT32 machines can write to the other NTFS machines - except the one with VISTA - because W2K and XP OS are compatible with both file systems. Since the VISTA OS can only be installed on NTFS, it is not compatible with FAT 32 file systems, and in a network any computers using FAT 32 will never be able to write to a computer with the VISTA OS. Is this correct?
"Andrew" wrote:

Vista does not support Fat partitions
"CathLB" wrote:
I've installed Windows Vista Beta 2 in a 5-computer network. 2 of the other machines are using the NTFS file system and 2 are formatted as FAT 32 file system. The machines (an XP SP1 and W2K) with NTFS can access, read, & write with no problems to shared drives on the Vista machine; the 2 machines, both XP SP1, formatted as FAT 32 can access, read, & copy but not write to the Vista shared drives. Could this be by design or a bug to be worked out in the Beta system? Has anyone noticed this? I've tried unchecking "Use Sharing Wizard" in Folder Options/View, but this had no effect.

CathLB do you have your shares setup with username and password?
"CathLB" wrote:

I've installed Windows Vista Beta 2 in a 5-computer network. 2 of the other machines are using the NTFS file system and 2 are formatted as FAT 32 file system. The machines (an XP SP1 and W2K) with NTFS can access, read, & write with no problems to shared drives on the Vista machine; the 2 machines, both XP SP1, formatted as FAT 32 can access, read, & copy but not write to the Vista shared drives. Could this be by design or a bug to be worked out in the Beta system? Has anyone noticed this? I've tried unchecking "Use Sharing Wizard" in Folder Options/View, but this had no effect.

Each computer in network requires username and password to logon. (One of the XP/FAT 32 computer has the exact same usernames/passwords as the Vista computer). I've tried turning the Guest account "On" on the Vista computer, but that had no effect. I would also like to add that the Vista computer has a second internal, shared, drive which is formatted as FAT32, and the other FAT32 computers cannot write to this drive either.
"Chris {MSVB Beta Support}" wrote:

CathLB do you have your shares setup with username and password?
"CathLB" wrote:
I've installed Windows Vista Beta 2 in a 5-computer network. 2 of the other machines are using the NTFS file system and 2 are formatted as FAT 32 file system. The machines (an XP SP1 and W2K) with NTFS can access, read, & write with no problems to shared drives on the Vista machine; the 2 machines, both XP SP1, formatted as FAT 32 can access, read, & copy but not write to the Vista shared drives. Could this be by design or a bug to be worked out in the Beta system? Has anyone noticed this? I've tried unchecking "Use Sharing Wizard" in Folder Options/View, but this had no effect.