Question for win2K users.

[everettes]

MoleDK:

It's rare you have to reboot Win2k to do anything other than install cards.

PhotoShop, Office 2000, and a slew of others with no reboot. Even the drivers for the SBLIVE didn't require a reboot.

------------------
Reach me on MS Messenger as everettes@hotmail.com
PIII550, Intel SE440BX-2, 2 x 128 Kingston PC100 ECC, 2940U2W, Seagate Cheetah, G400-32 SH, Plextor 8\20, Plextor 40Max, Pioneer 303s, SBLive!, MS FFPro, Altec Lansing ACS-48, Sony CDP 520GS

[paulcs]

You missed something in my post. "I'm running both Windows 2000 and Windows 98se on the same machine and, currently, *without a Matrox board.*" I could have worded this better. Sorry. It's early in California.

I'm been testing W2K with every board I can get my hands on: Matrox, 3dfx, nVidia.

Paul
paulcs@flashcom.net

[everettes]

MoleDK:

It's rare you have to reboot Win2k to do anything other than install cards.

PhotoShop, Office 2000, and a slew of others with no reboot. Even the drivers for the SBLIVE didn't require a reboot.

------------------
Reach me on MS Messenger as everettes@hotmail.com
PIII550, Intel SE440BX-2, 2 x 128 Kingston PC100 ECC, 2940U2W, Seagate Cheetah, G400-32 SH, Plextor 8\20, Plextor 40Max, Pioneer 303s, SBLive!, MS FFPro, Altec Lansing ACS-48, Sony CDP 520GS

[everettes]

I did something really stupid about two weeks ago. BetOS had posted ACTUAL WORKING test driver for the Voodoo 3 that were used by MS. I downloaded them, used them, and they WERE GREAT. Then like a dummy, cleaned my hard drive and mistook them for a junk file and DELETED the damn things. Now the drivers have been removed from that site. Only the hacked Banshee drivers are there now. I was KICKING myself all day. This was at the same time I was fighting this G400 to get it to work. If you can find someone that still has th MS drivers, the V3 really worked great. Now I'm stuck with nothing but 2d in Windows 2000. If I ever find the V3 drivers, I'll swap cards fast enough to cause a thunderclap.

PS: Just to prevent useless posts in response to this, I'm refering to V3 drivers that were available for a day or so on BetaOS. These were MS drivers, not the Toste drivers or other hacked drivers. Bt actual V3 drivers from MS and 3dfx.


------------------
Reach me on MS Messenger as everettes@hotmail.com
PIII550, Intel SE440BX-2, 2 x 128 Kingston PC100 ECC, 2940U2W, Seagate Cheetah, G400-32 SH, Plextor 8\20, Plextor 40Max, Pioneer 303s, SBLive!, MS FFPro, Altec Lansing ACS-48, Sony CDP 520GS

[HedsSpaz]

Hey Gurm, this is a little off topic, but could you jump back for a sec. You mentioned NTFS5. I haven't heard of this one, course it's probably just something that I missed somewhere along the line, and since I haven't played with win2k to much thats not suprising.
Anyway, what I was wondering is if you could describe how it works. I mean, I know that FAT32 drops to 4k clusters, which allows for more files to take up less space, and in turn allows larger partitions than FAT16. And likewise, I don't know how exactly NTFS works, but I know that it has the extra security options and and allows for larger partitions than FAT16 although not as big as FAT32.
So, is NTFS5 a hybrid of FAT32 and NTFS or is it something completely new?

Thanks
HedsSpaz


------------------
"I used to be indecisive, but now I'm not so sure." --Me

[everettes]

NTFS is just a different file system incorporating file system security and encryption, and a more stable structure based on file logging. Logging allow for a file to be Re-written with the updated file, and only after the newer file is verified is the older file written out. A file error would then result in the OS referring to the LOG to undo any changes. There by eliminating most corrupt files as a result of virii and bad sectors. The OS then Re-writes the file to a different sector. As opposed to FAT or FAT32 which could really care less. You don't find out you have corrupt data till you run scandisk or try to open the file. NTFS5 is just the newer version of NTFS used in NT4. WARNING, if you install Win2000 onto a PC running NT4 on a NTFS partition, the NT partition will be converted to NTFS5 by default. Rendering the data on that partition invisible to NT4.

PS, I left out the technical terminolgy to avoid confusing people. If Gurm can state it better, please do

[This message has been edited by everettes (edited 12 November 1999).]

[HedsSpaz]

I understand what NTFS and FAT32 are, and for the most part how they work, that isn't what concerns me though. You say that NTFS5 is just the newer version of NTFS. Fine, what I want to know is what, if anything, is new about it. Can it handle larger partitions than NTFS? Is there some fun new feature that would make me want to choose it over FAT32?

Sorry if I wasn't clear about that before, if you don't know I'll just go try and root it out of the MSDN libraries.

[xortam]

From MSFT web site ...

NTFS. The newest version of NTFS has a new on-disk file system structure that is included in the Windows 2000 operating system. This new structure is required to support many storage enhancements including volume mount points, remote storage, file system encryption, sparse files, and disk quotas. Windows 2000 setup handles the on-disk upgrade, and other system utilities are available for conversion of legacy file systems to NTFS. Windows NT® 4.0, Service Pack 4 and later includes an updated NTFS driver that may mount volumes with this updated NTFS format.

Many advanced services (AD, et.al.) in W2K require NTFS5. Its an IFS which supports encryption, HSM, etc. See http://www.microsoft.com/windows/ser...nt/StorDev.asp for more information.


[This message has been edited by xortam (edited 12 November 1999).]

[Rattledagger]

to HeadsSpaz:
Well, if we shall take the win2k resource kit (beta) as starting point:
In Windows 2000, the maximum file size and volume size for FAT32 is 32 GB.

AFAIK win9x-formatted larger than 32 GB should work. But why use fat32 on so big partitions?
NTFS-volumes can be as big as 2 TeraBytes.
NTFS has smaller default cluster-sizes than fat32. If I remember correctly:
512 bytes: < 512 MB
1k: 512 < 1G
2k: 1G < 2G
4k: all larger than 2G
The smallest default fat32-size is 4k.
You can manually format as cluster-size 512 bytes to 64k.
On NTFS you can compress individual files. Compression don't work for cluster sizes larger than 4k.
NTFS hasn't any "smallest" volume-sizes as fat32 has.