vipejc

Thanks for the intel, guys. Not that Intel. I'll get busy. Lots to read and do.

I want to archive every XP high-priority update and some optional XP updates. I also want to archive every Internet Explorer 8, .NET Framework 1.1 to 4, Media Player 11, etc., update. But there's so many and I have no idea how I would compile the list. The Microsoft Download Center doesn't even find some updates, but if you Google them, they're right there. Some updates supercede others, and I have no idea how to tell which updates are old or needed. Is there a folder or registry key that lists EVERY XP update I ever installed?

For technology I will agree. If you try looking up sports injuries or body parts/muscles you do not know, that is another story! While I agree to a point, everyone has their specialties. I think that given time, Jaclaz can possibly replace google since he has all the relevant links, while google likes to toss a bunch of other things in there, especially when it does that "we searched for this instead of what you typed, click here to actually search for what you typed in." crap. Yeah, Jaclaz is the new search engine. Best of all he's malware-free. Everybody has a purpose. Nobody knows it all. The intent of forums, just like MSFN, is to bring diverse minds together to solve all problems. Never be afraid to ask for help or feel stupid asking for it. We all learn in different ways and at different speeds. I never forget that and try to return the favor whenever I can. There's way too many idiotic things in this industry to keep it all straight, all the time.

Jaclaz, do you not eat, sleep or bathe and spend all your time reading computer Wikis and Microsoft Knowledge Base articles? Because you know an awful lot about technology.

WHY guessing? Wouldn't researching be more reliable? POSIX is a Windows NT subsystem: http://en.wikipedia.org/wiki/POSIX http://en.wikipedia.org/wiki/POSIX#POSIX_for_Windows http://en.wikipedia.org/wiki/Microsoft_POSIX_subsystem This is the "new version" of it: http://en.wikipedia.org/wiki/Windows_Services_for_UNIX (I have NO idea if this latter is 2038 compatible) PERL normally runs in the POSIX subsystem so it tests it (and not the actual NT). Well, actually I have worked on ANY Windows version, starting from 1.0, but NOT in the sense you seem to think the "developer" label has been given to me on MSFN, but I am NOT a developer, at the most I put a couple of lines of batch together (and PUSH "real" developers to do their work ) You must be joking. I am a dinosaur, one of the most advanced videogames I ever played has been (very recently) this one : jaclaz I do try to research everything. The problem is Wikipedia and everywhere else make simple stuff into a book and use developer speak that I can't understand. They take all the fun out of learning. First I get mad. Then I laugh at them...like I'm about to do now. LOL You had me fooled good. Why with your high-level tech talk, eccentric yet sarcastic approach to help desk, and constant Wikipedia links, I really thought you were a Developer. A non-developer with a developer title. That's like a man with a needle calling himself a doctor. Wouldn't your proper title be Project Manager? And please explain how the "developers" could allow another Y2K, when it all it took to prevent the first one was setting the start of time to 0. LMAO

Jaclaz, I'm guessing POSIX isn't used in Windows NT? You being a Developer, have you worked on any versions of Windows? Any videogames?

Most probably it won't even actually crash, it will simply create/display/print/whatever "silly" dates, or, if dates are used for internal calculations, show/etc. "silly" results. jaclaz I'm setting up a test environment and will report the results. I'll also be contacting all software vendors I support and asking them to use an unsigned 32-bit integer for time_t in a future version, to postpone the problem until 2106, which is the best compromise, because nobody in that generation will know XP, and thus can't have an attachment to it. Huh? I thought Windows NT was immune from Y2K38? Then what's this: What operating systems, platforms, and applications are affected by it? A quick check with the following Perl script may help determine if your computers will have problems (this requires Perl to be installed on your system, of course): #!/usr/bin/perl # # I've seen a few versions of this algorithm # online, I don't know who to credit. I assume # this code to by GPL unless proven otherwise. # Comments provided by William Porquet, February 2004. # You may need to change the line above to # reflect the location of your Perl binary # (e.g. "#!/usr/local/bin/perl"). # Also change this file's name to '2038.pl'. # Don't forget to make this file +x with "chmod". # On Linux, you can run this from a command line like this: # ./2038.pl use POSIX; # Use POSIX (Portable Operating System Interface), # a set of standard operating system interfaces. $ENV{'TZ'} = "GMT"; # Set the Time Zone to GMT (Greenwich Mean Time) for date calculations. for ($clock = 2147483641; $clock < 2147483651; $clock++) { print ctime($clock); } # Count up in seconds of Epoch time just before and after the critical event. # Print out the corresponding date in Gregorian calendar for each result. # Are the date and time outputs correct after the critical event second? I have only seen a mere handful of operating systems that appear to be unaffected by the year 2038 bug so far. For example, the output of this script on Debian GNU/Linux (kernel 2.4.22): # ./2038.pl Tue Jan 19 03:14:01 2038 Tue Jan 19 03:14:02 2038 Tue Jan 19 03:14:03 2038 Tue Jan 19 03:14:04 2038 Tue Jan 19 03:14:05 2038 Tue Jan 19 03:14:06 2038 Tue Jan 19 03:14:07 2038 Fri Dec 13 20:45:52 1901 Fri Dec 13 20:45:52 1901 Fri Dec 13 20:45:52 1901 Windows 2000 Professional with ActivePerl 5.8.3.809 fails in such a manner that it stops displaying the date after the critical second: C:\>perl 2038.pl Mon Jan 18 22:14:01 2038 Mon Jan 18 22:14:02 2038 Mon Jan 18 22:14:03 2038 Mon Jan 18 22:14:04 2038 Mon Jan 18 22:14:05 2038 Mon Jan 18 22:14:06 2038 Mon Jan 18 22:14:07 2038

No misunderstanding here. Of course I'll be using XP in 2038 and beyond. It was my question. LOL Since XP uses 64-bit time, if I were to adjust Windows' Date and Time to the year 2040 to check that all my programs are safe or not from Y2K38, what is the worst that could happen? Could XP crash, even though it's immune from Y2K38, or would just the offending program crash, like any other protected-mode error?

My BIOS' date goes all the way to 2099. I will have my 32-bit Windows XP Home w/ SP3 CD placed in my cold, dead hands before the lid to my coffin is closed and I am lowered into the ground.

I'm positive. Enjoy your Windows 25 with space communication.

Sometimes Windows Update fails to install an update because you didn't install the dependent software in a specific order. I found this out after a .NET Framework 1.1 update failed to install. After uninstalling all the .NET Frameworks and reinstalling them, starting with 1.1 and then downloading the patch before .NET Framework 2.0, the patch passed.

Since Windows NT, including XP, use a 64-bit time integer for file and system time, are all programs for them safe from the Y2K38 problem?

The CoolerMaster case manual doesn't have a front panel pinout. Another problem is CoolerMaster and the OEM use different terminology to describe identical wires, so I don't know if the pins are identical or different. No, my motherboard has two integrated USB 2.0 connectors. It seems as if the case's USB connectors are compatible, but the AC'97 audio and IEEE 1394 are incompatible. I want to be sure so I don't damage my motherboard.

Question is title.

submix8c' timestamp='1301540044' post='961192'] No, I want to integrate all XP and other updates that go with XP using nLite and make a master XP install DVD, but that doesn't seem possible, as I've read an integrated update breaks something or the update can't be integrated. I already have an XP CD with SP3 slipstreamed. At this point, I'm just playing the waiting game, and in late 2014 when XP updates are done and the mod makers smooth it all over, that's when I'll do that.

This is a prime example why I rarely use Windows Update. Don't fix it if it isn't broken. Unless you absolutely need an update, don't run the risk. An unstable update can wreck havoc on a system, especially if you install a bunch of updates at a time and then have to pinpoint a problematic update. I use an AMD Athlon XP 3000+ with XP.

If I have MSXML 4.0 Service Pack 3 installed, do I need MSXML 4.0, MSXML 4.0 Service Pack 1, or MSXML 4.0 Service Pack 2, also? If I have Microsoft Visual C++ 2008 Redistributable Service Pack 1, do I need Microsoft Visual C++ 2008 Redistributable, also? If I have Microsoft Visual J# .NET Redistributable Package 2.0, do I need Microsoft Visual J# .NET Redistributable Package 1.1, also?

Because an in-place upgrade requires reinstalling all Service Packs and Windows' updates.

The first question you must ask yourself is "What are my needs?" UT2004, word processing, 2D Web browsing, and the like? If so, an AMD dual core CPU and video card with ATI Radeon X1300-1950 GPU will be just fine.

This does work.Beside hal there is kernel, chipset, cpu and custom drivers. Old and new hardware is importand. A backup would be nice too. I can find plenty of articles on how to migrate an XP installation from a WORKING SOURCE SYSTEM to DESTINATION SYSTEM, but not one on migrating XP from an IMAGE OF A DOWNED SYSTEM to destination system. So it can be done, but how? Exactly what hard disk controller data needs to be changed in the Registry to make this procedure successful? How do we set the offline Registry data for XP so it uses Windows' standard drivers, such as the Dual Channel PCI IDE Controller?

That's exactly why I do NOT want to perform an in-place upgrade. I wonder if my theory would work: manipulate the Registry offline using BartPE (hard disk controller data); delete "hal.dll" from the system32 folder, replace with correct HAL file, and rename "hal.dll"; and then reboot.

Jaclaz, my motherboard failed and I don't have a backup system. I want to set my XP installation to use Windows' Standard Dual Channel PCI IDE Controller and change the HAL, without reinstalling or performing an in-place repair. Is this possible using BartPE or any other tools?

I'm doing this manually, without the fixIDE plug-in. Could I just add all the registry info for each XP-supported IDE controller on a live system without upseting the currently used IDE controller? If so, how would I do that?

ACPI Multiprocessor PC ACPI Uniprocessor PC Advanced Configuration and Power Interface (ACPI) PC Compaq SystemPro Multiprocessor or 100% Compatible PC MPS Uniprocessor PC MPS Multiprocessor PC Standard PC Standard PC with C-Step i486 Other

I want to add all the XP-supported IDE controllers. I copied this into Notepad and named the file XP IDE controllers.reg. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\primary_ide_channel] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="atapi" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\secondary_ide_channel] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="atapi" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*pnp0600] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="atapi" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\*azt0502] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="atapi" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\gendisk] "ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}" "Service"="disk" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#cc_0101] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_0e11&dev_ae33] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_0601] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1039&dev_5513] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1042&dev_1000] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_105a&dev_4d33] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0640] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646&REV_05] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0646&REV_07] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0648] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1095&dev_0649] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1097&dev_0038] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0001] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10ad&dev_0150] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5215] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5219] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_10b9&dev_5229] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="pciide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_1106&dev_0571] "Service"="pciide" "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1222] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="intelide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_1230] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="intelide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2411] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="intelide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_2421] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="intelide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7010] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="intelide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7111] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="intelide" [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CriticalDeviceDatabase\pci#ven_8086&dev_7199] "ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}" "Service"="intelide" ;Add driver for Atapi (requires Atapi.sys in Drivers directory) [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\atapi] "ErrorControl"=dword:00000001 "Group"="SCSI miniport" "Start"=dword:00000000 "Tag"=dword:00000019 "Type"=dword:00000001 "DisplayName"="Standard IDE/ESDI Hard Disk Controller" "ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\ 52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,\ 00,73,00,79,00,73,00,00,00 ;Add driver for intelide (requires intelide.sys in drivers directory) [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\IntelIde] "ErrorControl"=dword:00000001 "Group"="System Bus Extender" "Start"=dword:00000000 "Tag"=dword:00000004 "Type"=dword:00000001 "ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\ 52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,6e,00,74,00,65,00,6c,00,69,\ 00,64,00,65,00,2e,00,73,00,79,00,73,00,00,00 ;Add driver for Pciide (requires Pciide.sys and Pciidex.sys in Drivers directory) [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PCIIde] "ErrorControl"=dword:00000001 "Group"="System Bus Extender" "Start"=dword:00000000 "Tag"=dword:00000003 "Type"=dword:00000001 "ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\ 52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,\ 00,2e,00,73,00,79,00,73,00,00,00 Do I merge this .reg file into the local system's Registry through BartPE, and then all XP-supported IDE controllers are usable?