bphlpt

Sorry I can't help you more right now, Kel. I'm dealing with helping my mom get moved into assisted living due to dementia, sciatica, failing health, and old age in general. I'm glad your health has improved lately. Good luck in your fund raising. I hope you are able to get the house. Cheers and Regards

are you referring to driverpack solution? http://driverpacks.net/docs/driverpack-solution I thought he was referring to SAD2. Cheers and Regards

I would think tha MS Office would be the biggest space hog. Cheers and Regards

Welcome to WinCert! Cheers and Regards

Sorry, but I still don't understand your problem. Do you want that behavior or not? If chkdsk runs at every boot, then you must have set it up to do that. Did you? If you don't want it to happen any more, then can't you stop it from happening? I'm confused. Cheers and Regards

So, to save anyone else from also having to do a lot of search, what did you find? How were you able to do it successfully? Can you tell us and/or share a link to what you found? I would love to be proved wrong. Cheers and Regards

Welcome to WinCert! Cheers and Regards

I have un-hidden all of the older versions that were uploaded to the download page since the start of 2013. For those that haven't found which page they are listed on, it is this one, which is the main Win Toolkit download page. The one on the top is they latest version, and the older versions are available on the right. [ NOTE: Liam, the writeup on that page says that .NET 3.5 is required for XP and Vista users, but isn't .NET 4.0 required now? If so, that note should be changed and an appropriate link should be provided.] Cheers and Regards

So isn't CHKDSK sufficient? I don't know of any other general-purpose free tool available to fully check a disk and possibly correct errors found or mark block that have errors that are not correctable. There might be manufacturer specific tools available for specific brands of drives. Maybe others are aware of something else. Lets us know if you find anything. Cheers and Regards

I have many of them as well, but not all. Liam, I seem to remember at least one time when all the "hidden" versions were displayed on the download page, but not now. If you could tell me, via PM, how to "un-hide" the versions that are there, I'll be glad to do the work to un-hide them, if you wish. I suppose I could also upload any of the missing ones that I happen to have, but I'm not sure that all the old versions are necessary. It might just be more confusing for new users. Just let me know. Cheers and Regards

????? I'm not sure what you are asking for. Cheers and Regards

I'm afraid I don't understand what you are saying/asking for. I have no idea what you mean when you say you want "the last update of Microsoft(8/2/2014)". [February 8, 2014??] What is that? Then you say "I'm not interested in this topic". What topic? And "I read on that site". What site? Then you quote something that is talking about the recently found trick to allow updates that were originally intended for Windows Embedded or POSReady 2009, which are based on XP SP3 and are scheduled to continue to receive updates until 2019, to be applied to XP. Yes, those updates have not been fully tested against Windows XP itself, but I have heard no reports that any of those updates have caused any problems whatsoever. But I can't tell, do you want to use those updates or not? AFAIK, the pack made by user_hidden, what this thread is about, does NOT have any of the updates intended for Windows Embedded or POSReady 2009, but ONLY those updates intended for XP. So if that kind of pack is what you want, then this is the thread for you. Cheers and Regards

Congratulations © KEiGHT! But there still seems to be some figuring out needed, since the original format of the date is MM/DD/YYYY, from looking at the images from abbodi1406, and the format you ended up with in the image above is DD.MM.YYYY, unless that is the format you always see and it is dependent on some local date setting of your machine? Just curious and trying to get it perfect. Cheers and Regards

It all depends on WHERE you are when you open the command prompt: (or what the value of your %PATH% is set to.) ie, C:\Temp>cscript DateToInteger8.vbs "06/09/2014 10:30:00 PM" But your suggestion of including the full path to the script is more foolproof. Thanks. I'm glad you got it working. EDIT: I think this might be a useful option for Liam to include in Win Toolkit, assuming there are no problems caused by it. Automating the process would be a lot easier for the average user. Cheers and Regards

1 ) Take the DateToIntegr8.vbs script above, (just delete the .txt part of the name) and save it wherever you want, say C:\time. 2 ) Then open a command prompt in that directory. 3 ) Enter the following command: cscript DateToInteger8.vbs "06/09/2014 10:30:00 PM", where the date and time are that of your local time zone 4 ) Use calc.exe (programmer mode) to convert to hex (QWORD) - Enter the output from DateToInteger8, which will be a decimal value, in the calculator in decimal mode, then switch modes to hex to see the hex value you need. 5 ) @KEiGHT, in his local time zone got: 1CF842195DB5400 6 ) You can validate that the value you have is correct by entering in the command prompt: w32tm /ntte 0x1CF842195DB5400 7 ) @KEiGHT, in his local time zone got: 151004 20:30:00.0000000 - 6/9/2014 10:30:00 PM 8 ) Zero pad the value from the calculator to get 16 digits: 01CF842195DB5400 9 ) The leftmost 8 digits will be the highpart (01CF8421) and the rightmost 8 digits will be the lowpart (95DB5400). I'm not sure if the date displayed in the OS version selection window is that of your local time zone or GMT, so you might have to adjust the values you enter above slightly, but since the output from w32tm includes GMT you should be able to figure out what you need to change. So you found the .xml file where you need to enter this revised value? Where is it? Cheers and Regards

I haven't done it, but look here, then read the rest of the thread to see how to calculate exactly what to put there. Cheers and Regards

Windows XP itself no longer has any official updates. Some of the various security addons such as the Malicious Software Removal Tool still seem to get updates. But POSReady 2009, which is based on XP SP3, is still scheduled to receive updates until 2019, and there has been a trick discovered that allows your XP installation to appear to be POSReady 2009 to Windows Update, so the POSReady 2009 updates can be downloaded and installed to your XP installation. Does that answer your question? Cheers and Regards

Cheers and Regards

I ask again: Even if it would take awhile to do, it would take less time than the 35 days since I last suggested it to you. I know of no specific instructions to give you even if you did want to try to do this. I'll let someone else comment if they have any ideas, but since no else has commented on this thread I wouldn't hold your breath. Good luck in your efforts. Cheers and Regards

This one worked for me this time, but I don't know if one success is a sufficient test. Besides, my experience in the last several months has been that the bigger the download the more likely that there will be a problem, and this one is not too big. Cheers and Regards

Welcome tt WinCert! If, after a few days, you don't get enough responses to your questions, you might try posting a similar question in the Win Toolkit subforum, because I think I remember at least one other member, ThuGie, who has also been working on updating his Vista install source using Win Toolkit. I could also move this thread over there if you prefer, just let me know. In the meantime, you might want to see if you can find some of ThuGie's posts that talk about his efforts and start a dialogue. It is OK to share links for ISO's that might be useful or for other sites that talk about them, but only if they are legitimate ISO's from approved MS sources, ie places like DigitalRiver or other MS direct links and not torrents or places like MediaFire. Please read our Forum Rules, especially rule #1. Good luck in your efforts. EDIT: LOL We cross-posted. Can you share a link to the ISO you found, or at least list the complete official name of the ISO? Cheers and Regards

But you might could copy DISM from the mounted image to the host system and run it from there, even if you copied it to a temporary location that you later deleted? But I don't know if simply copying it would work compared to having it officially installed. Cheers and Regards

By the way, I haven't had a chance to debug it further, but the PowerShell version, which is invoked from a CMD box with: ( assuming it is run from the folder where PSDateToInteger8.ps1 is located ) powershell "& .\PSDateToInteger8.ps1 ""06/09/2014 10:30:00 PM"""seems to have an issue properly detecting whether Daylight Savings Time is in place(?), because when you try to "validate" the results using w32tm it is off by an hour. The .VBS version works correctly. Actually I'm not sure which of the functions is correct, but at least the .VBS is consistent with w32tm. And if you comment out the "Correct for daylight savings." section in the code of the PowerShell version then it gives the same results as the .VBS version. Cheers and Regards

Thanks! Your solution is obviously from the same guy, of course. LOL Just his VBS version of his PowerShell solution. Cheers and Regards

For me: w32tm /ntte 0x1CF83BD00A67400 151004 08:30:00.0000000 - 6/9/2014 4:30:00 AM 151004 08:30:00. <- GMT ... 6/9/2014 4:30:00 AM <- relative to GMT (system setting > UTC-05:00 Eastern time Zone and Daylight Savings Time is in effect ) Is there a switch in w32tm that converts in the other direction? ie human readable local or GMT to highpart/lowpart? Looking only very briefly I didn't see one. Or maybe a different command? Just curious. EDIT: I did find a discussion here, which includes a PowerShell script here, which looks like it does the job, so maybe there is not an easier way? For convenience the PowerShell script: # PSDateToInteger8.ps1# PowerShell script demonstrating how to convert a datetime value to the# corresponding Integer8 (64-bit) value. The Integer8 value is the# number of 100-nanosecond intervals (ticks) since 12:00 AM January 1,# 1601, in Coordinated Univeral Time (UTC).## ----------------------------------------------------------------------# Copyright (c) 2011 Richard L. Mueller# Hilltop Lab web site - [url=http://www.rlmueller.net/]http://www.rlmueller.net[/url]# Version 1.0 - March 19, 2011## You have a royalty-free right to use, modify, reproduce, and# distribute this script file in any way you find useful, provided that# you agree that the copyright owner above has no warranty, obligations,# or liability for such use.# Read Datetime value from command line or prompt for value.Param ($strDate)If ($strDate -eq $Null){$strDate = Read-Host "Date (Local Time)"}# Convert string to datetime.$Date = [DateTime]"$strDate"# Correct for daylight savings.If ($Date.IsDaylightSavingTime){$Date = $Date.AddHours(-1)}# Convert the datetime value, in UTC, into the number of ticks since# 12:00 AM January 1, 1601.$Value = ($Date.ToUniversalTime()).Ticks - ([DateTime]"January 1, 1601").Ticks$Value Cheers and Regards