Kalo, I don't know that FDV's thinking is the same as mine but I can tell you why I am excited that he is already tackling 2K3: obsolesence. There will come a time when 2K either isn't capable of doing the things we need/want (IPv6) or when it just isn't supported by vendors anymore (more likely). Make no mistake...we'll have to upgrade sooner or later. How about this theory for a bright light in the tunnel?
Didn't you also make a graph recently that compared feature sets to 'competing' projects? I found that, as well as your mem shots, very interesting. These products look like the makings of a great marketing campaign!
From NT Compatible: http://www.ntcompatible.com/April_2006_Sec...age_s66225.html This ISO-9660 CD image file contains the security update for Windows released on Windows Update on April 11th, 2006. This does not contain security updates for other Microsoft products. This CD image is intended for corporate administrators who manage large multinational organizations, who need to download multiple individual language versions of each security update, and who do not use an automated solution such as WSUS. Use this image to download multiple updates in all languages at the same time. Caution: Be sure to check the individual security bulletins at http://www.microsoft.com/technet/security prior to deployment of these updates to ensure that the files have not been updated at a later date. >> April 2006 Security Release ISO Image
From a network admin perspective, it is good that users cannot change the time. It is tough to schedule maintenance, defragging, patching, etc when joe blow changes his time to something crazy or dorks up the DST option.
Chalk up another vote for Vector/Kubuntu. I would use vector as a workstation and Kubuntu as a server, although both can perform either duty adequately.
Something like HFSLIP_LOG.txt may be more descriptive. It isn't *really* an error report, anyway. The output assists in diagnosing errors that come up. I haven't really seen anywhere that HFSLIP outputs useful error information...unless that is a diagnostic mode for it. It might be handy to have all of those 'file not found' and other such errors that go flying by get dumped into a real error_report.
I use this feature. It is quite handy whenyou have lots of ISOs laying around from a lengthy bug-squashing session. Since the root error_report gets overwritten, the ISO copy provides a great snapshot of what that ISO represents. I agree with you and would still like to see the compressed error_report
That is almost exactly what I was thinking. Also, I have both expand.exe and extract.exe on my 2kSP4 box. expand.exe is version 5.0.2134.1 and 15,632 bytes extract.exe is version 1.00.603.0 and 93,242 bytes
This is an interesting idea, and one that would have saved me TONS of trouble early in my HFSLIP days since I had a similar issue. The script could also be made to check the filesize and compare it to "known good" filesizes of extract.exe.