speed up my pc 2012 free download for windows 7spore galactic adventures download free fullwindows xp professional 2006 service pack 2 free downloadunreal gold patch download
100% Virus-Free and Spyware-Free Guaranteed!
Note : MiniTool Partition Wizard Business Edition version 4.2.2 or older version isn't supported.
MiniTool Partition Wizard Free Edition is usually a free partition manager software made by MiniTool Solution Ltd.
Windows XP, 2000 Professional, Vista SP2, Windows 7 SP1, Windows 8 and Windows 10all editions, 32 bit and 64 bit
MiniTool Partition Wizard Professional Edition could help manage both basic disk and dynamic disk; it could actually work as the modern partition magic for Windows 8.1/7/vista/XP.
Windows XP, 2000 Professional, Vista SP2, Windows 7 SP1, Windows 8/8.1 and Windows 10all editions, 32 bit and 64 bit
MiniTool Partition Wizard Server Edition is often a server partition manager specially engineered for Windows Server 2000/2003/2008/2008 R2.
Windows 10, Windows Server 2000 SP4, 2003, Home Server, 2008 R2, Windows Small Business Server 2003, 2008, 2011, Windows XP, 2000 Professional, Vista SP2, Windows 7 SP1 and Windows 8, Windows Server 2012 R2all editions, 32 bit and 64 bit
MiniTool Partition Wizard Enterprise Edition is ideal for organizations, companies, schools and governments.
Windows 10, Windows Server 2000 SP4, 2003, Home Server, 2008 R2, Windows Small Business Server 2003, 2008, 2011, Windows XP, 2000 Professional, Vista SP2, Windows 7 SP1 and Windows 8, Windows Server 2012 R2all editions, 32 bit and 64 bit
MiniTool Partition Wizard Bootable CD allows user too computer right into MiniTool Partition Wizard to control partitions without limitations.
Windows 10, Windows XP, 2000 Professional, Vista SP2, Windows 7 SP1 and Windows 8all editions, 32 bit and 64 bit
MiniTool Partition Wizard Bootable CD for Windows Server allows users as well server right into Partition Wizard Server to manager partitions.
Windows 10, Windows Server 2000 SP4, 2003, Home Server, 2008 R2, Windows Small Business Server 2003, 2008, 2011, Windows XP, 2000 Professional, Vista SP2, Windows 7 SP1 and Windows 8, Windows Server 2012 R2all editions, 32 bit and 64 bit
Solution Ltd., All Rights Reserved.
Posted: Fri Jun 06, 2014 11:57 am Post subject:
Congrats, still makes me otherwise anyone an enormous WOW of how far this progress may be gone so well, I cant believe its June Already, feels the same as yesterday the reason is February or January that you simply couldnt develop it most of you would have liked and here i am, BETA 2 in June.
Only when we could tell depends upon about this like NBC or Facebook for getting this so well received other than the regards of Microsoft may attempt to disrupt this pattern.
Congrats to everyone testing this thing out and guidelines to keep it windows alone with virtually no 3rd party programs like safari, chrome, other codecs wouldve been great thou, etc.
Posted: Fri Jun 06, 2014 4:17 pm Post subject:
Its just finished uploading. I accidently screwed up the initial sfxcab installer, thats why I was required to reupload the file.
Posted: Fri Jun 06, 2014 5:07 pm Post subject:
Thank you greatly harkaz!
Now that SP is basically in its final form, could I possibly impose upon you to definitely please list the differences of the is built into SP4 vs OnePieces pack? Both what his has that SP4 isn't going to and the opposite way round if you could. TIA I would believe info, together with the list of precisely what is in the pack for example you as listed above, can be good things to include inside main post in the threads concerning SP4 wherever you post them and inside the documentation also.
As to documentation, it may also be helpful to include basic descriptions on the various proven methods that SP4 is usually incorporated into an XP build, both live and offline, as well as the tools which were proven to work effectively with such builds and SP4, including nLite and RVMi, and WinNTSetup along with other tools when they have been been proven. Such info could possibly head off lots of How do? type questions from new users. The fact you have made SP4 to a service pack that may be installed and uninstalled in countless ways including offline and live both with and without resorting to external tools should make SP4 the most preferred method for making XP builds, IMHO. Im sure you will see some that could not want certain features, such or whatever, therefore you should probably describe which features is usually removed, either once installed, or taken from SP4 before installation, crowd possible. I believe that OnePieces pack provides the ability to colorize it for you somewhat by doing so, but I could possibly be wrong. As you recognize, I always are interested all so I have not tried to accomplish that, but it could broaden SP4s appeal it it were possible. If not, you might also spell out now to protect yourself from the various Can I? kind of questions. Just a thought.
Posted: Sat Jun 07, 2014 7:27 am Post subject:
The whole project is extremely good!
Windows XP SP4 probably will be familiar with install on many old PCs simply with CD ROMs so, fit:
What I should do, for getting XP SP4 on one CD from 700 MBs?
Harkaz employ a solution for splitting on two CDs but I dont identified do I need both CDs for installation or CD 2 should be used only when I have to install tablet/mediactr components?!
However its obvious a large number of people dont need media center or tablet computer components whatsoever, but people need net frameworks, directx,
So, in Beta 2 version of USP4 the issue is SOLVED!!!
And you'll get clean XP SP4 688 MB ISO.
Posted: Sat Jun 07, 2014 8:25 am Post subject:
1. Live installation Ability: USP4 - Supported, SP1/SP2/SP3 is usually installed for the systemOPWXPUP - Not supported
2. Slipstream in numerous XP sources: USP4 - All Windows XP sources at any SP level apart from Embedded-based builds - Starter, Home, Home K, Home KN, Home N, Professional, Professional K, Professional N, Professional KN, Media Center 2002/2004 SP2/2004 SP3/2005, Tablet PC 2002/2005
vs OPWXPUP: Home SP3, Professional SP3, MCE2004SP3/MCE2005 SP3, Tablet PC 2005 SP3.
3. Included components differences: i OPWXPUP isn't going to include MSN Explorer 10.5 - built into USP4.
iv Tablet PC 2005 Framework 1.0 SP3 all updates are contained in USP4
v USP4 will not include Windows Powershell 2.0 being an optional component.
vi DX Redistributable 2010 is just not uninstallable in USP4, nevertheless it is an optional component in OPWXPUP.
Framework 2.0, DirectX for Managed Framework 3.0 Framework 3.5 are seperate components in OPWXPUP.
Framework uninstallation is just not MSI-based in USP4. This helps avoid some complications with MUI packages.
ix USP4 includes XPS Viewer and XPS Document Writer to be a seperate component - XPS Viewer not a part of OPWXPUP, XPS Document Writer is an element Framework 3.0
x Windows Search 4.0 and Windows Genuine Advantage Notifications are disabled automagically in USP4 - but enabled in OPWXPUP.
xi No Brower choice, XP End of life notification optional components in USP4.
xii POSReady registry tweak enabled in USP4, not a part of OPWXPUP - available for an addon.
xiii Ieaccess component takes care in the new tabs bug in USP4. The IE8 desktop icon behaviour is default in USP4, and not in OPWXPUP.
xiv USP4 won't include an solution to remove IE8 or WMP11.
xv With framework 4.0 are not enabled in Media Center edition. With OPWXPUP there just isn't such limitation, though it can cause MCE functionality issues.
xvi No need for IE8 cosmetic addon in USP4.
xvii In Framework 4.0 installer will not run the executequeueditems command. This command is executed in OPWXPUP - it could increase installation in time OPWXPUP- but improves system boot time. To improve system boot period in USP4, you must execute this command Framework 4.0 has become completed along with your computer is restarted.
xviii In USP4 Framework 4.0 installation commands are executed during Runonce T13 of Windows Setup. This fixes problems with SQL Server 2008 installation.
xix Microsoft Update Catalog is built into OPWXPUP. Not incorporated into USP4.
xx Updated OC icons for IEAccess, WMPAccess components in USP4.
xxi MRT is not contained in USP4.
xxii GDI Detection tool is not a part of USP4.
xxiii Organize Favorites IE8 hotfix is built into USP4/not incorporated into OPWXPUP.
Framework 1.1 just isn't removable in MCE2005 with USP4/OPWXPUP won't include this kind of limitation.
4. Clean and Upgrade Installation differences:
i The KB911610 text-mode setup fix is a part of USP4.
ii Time zone update registry is placed in text-mode setup phase.
iii Some registry keys for specific updates ie exFAT, kernel dump hotfix, etc. are positioned in text-mode setup. In OPWXPUP all update registry keys are incorporated GUI-mode setup.
iv In USP4 catalog files are not inside SVCPACK folder. No SVCPACK folder can be used by USP4.
v In USP4, catalog files are set up on T-39 phase of GUI Setup.
vi, and then modified files are digitally signed in USP4.
vii OC Components are digitally signed in USP4. In OPWXPUP reports unsigned file errors.
viii In Upgrade/Repair installations with USP4, qfecheck will function successfully following the upgarde. In OPWXPUP, updates wont be shown by qfecheck following your Upgrade.
ix WebDAV update is built into USP4. OPWXPUP doesn't include the WebDAV update.
x Installation time is shorter in USP4, a result of the Framework 4.0 installation method.
5. Root certificate update: November 2013 in USP4, November 2013 March 2014 in OPWXPUP.
6. OPWXPUP won't Framework 1.1 and Windows XP post-EOL updates. In USP4 all hotfixes until May 2014 are integrated, including post-EOL ones.
Last edited by harkaz on Sun Jun 08, 2014 1:41 pm
Posted: Sat Jun 07, 2014 8:39 am Post subject:
Harkaz, Im very impressed yet again. Not simply with the new beta, and also with your comparison of sp4 and also the OnePiece pack.
Running SP4 using a freshly installed XPSP3 works well with me as using the previous beta, but Im interested more in integrating SP4 into my XPSP3 source and inatallation with WinNTSetup.
I was happily surprised to notice that the revolutionary beta do not have any textmode missing files anymore. Im faraway from an expert within this, but I guess it implies the issue is solved now, which is wonderful!
However, installing with WinNTSetup still provided the same errors during gui install:
T-16: Windows cannot load the Internet Configuration Library. The following error occurred: The specific module could hardly be found.
T-13: Cant access the required device, path or file
After final reboot: Your current security setting do not let this file being downloaded.
The system then hangs with the Please screen.
Once again: This is probably WinNTSetup related, you are able to just signify that this will not likely work so we cant use WinNTSetup because of this, Im just
Im very enthusiastic about other peoples reports, did everybody use CD-based installs?
Posted: Sat Jun 07, 2014 12:01 pm Post subject:
atari800xl Please send me the and setuperr, log files on the WinNTSetup install attempt.
The just isn't part of Windows XP, so something else entirely
Probably I have to sign ALL files including dosnet, TXTSETUP
Posted: Sat Jun 07, 2014 12:34 pm Post subject:
I did more integrate and installs in numerous scenarios so Im not sure now about all.
The last integrate and install from USB expressed by WinSetupFromUSB was probably the most succesful. No errors, clean Event Viewer, nothing in, no unsigned in
I want to do a new install from a similar source but from ISO being sure that all is well.
Product Framework 3.0 Service Pack 2 - - Error 1309. Error reading from file System error 3. Verify that this file exists and that you just can jump on.
If I integrate from cmd the key just isn't recognized as valid.
Posted: Sat Jun 07, 2014 2:33 pm Post subject:
ianymaty To ensure proper slipstreaming, you must do it at a Windows XP system. Are you slipstreaming in a very running Windows XP system?
Posted: Sat Jun 07, 2014 2:47 pm Post subject:
is it like possible once i added my drivers and adding some more drivers with drivermax using restore option after windows installed, is it feasible that i corrupted somthing within the process when getting a sonyvegas windows error sign every time i try and opened it?
I employ a seperate hard disk which i dont use to maintain my normal drive safe to simply testing it on my machine.
plann to help you my 2 brothers because of their windows xp machines besides myself.
sry to the big img, didnt kno it turned out gonna do tat
Last edited by Anthony21 on Sun Jun 08, 2014 2:59 am
Posted: Sat Jun 07, 2014 2:47 pm Post subject:
I just noticed a fatal downside to XP Home CD-ROM installation. I will re-release Beta 2 with this particular fix and a few others.
Anthony21: I are unsure that. Most likely it's just not not an issue of XP SP4, however, because along with other driver-related files are signed.
Posted: Sat Jun 07, 2014 3:50 pm Post subject:
However in TXT Setup mode EULA still sey: Service Pack 3, maybe some mark here, like with Unofficial Service Pack 4 included or only Service Pack 4?
Posted: Sat Jun 07, 2014 4:27 pm Post subject:
However, installing with WinNTSetup still set it up the same errors during gui install:
T-16: Windows cannot load the Internet Configuration Library. The following error occurred: The specific module could hardly be found.
T-13: Cant access the required device, path or file
After final reboot: Your current security setting don't allow this file being downloaded.
The system then hangs with the Please screen.
Im very enthusiastic about other peoples reports, did everybody use CD-based installs?
Windows cannot access the required device, path or file. You may noy have appropriate persmissions to reach the item.
Posted: Sat Jun 07, 2014 4:44 pm Post subject:
I have to examine your and files.
This issue might not be fixed within the upcoming Beta 2a re-up.
Posted: Sat Jun 07, 2014 7:23 pm Post subject:
Actually Im likely to release a Beta 3 build, because from the many fixes.
Please continue testing the Beta 2 build and send me the and files.
The Custom setup installation can be a rather good test. It has shown me absence of some references in In addition, I need to abandon the written text mode insert second CD-ROM option, as it won;t are employed in custom install. A HIDDEN OC in T-26 has a great balance. This means one more INF, additional signing, references to DOSNET/LAYOUT/TXTSETUP and changes of
Posted: Sat Jun 07, 2014 10:10 pm Post subject:
ok, i really tested without worrying about drivers, didnt work, so I tested the actual iso with the xp machine my business is currently using while using same integration u showed me to make use of in go to add sp4 compared to that iso then instead on the msn ver., still cam up as failed, in comparison to with sp4 without having installments from a drivers when compared with our old dell pc with sp3 32 bit and didnt install sp4 to this particular pc yet, it functions.
and so i looked throu my installed programs we have under my windows 7 sp3 dell, only thing that ringed a bell was microsoft silverlight, therefore the sp4, i installed driver wireless card and also got silverlight, still with error, only thing that might comes to mine on my own list whether or not this isnt c witch i believed it said being forced to have it to operate sont, isnt listed, i had been thinking it might be Microsoft Compression Client Feature Pack 1.0.
besides that, i believe that its sp4 but cant b sure it and it also probably will be the layout u mention whitch im not sure a few things i could do on my small end to have sony workn.
here will be the stuff i have set up on dell and it is workn, i understand a few things that sony vegas uses but whats listed here, im not sure whats beeing made use of by it to work
Posted: Sat Jun 07, 2014 10:57 pm Post subject:
Anthony21, Have you experimented with uninstall Sony Vegas then reinstall it? Is there every other app you could have installed, or possibly a feature with the OS itself, which has a problem?
Posted: Sat Jun 07, 2014 11:08 pm Post subject:
I dont usually use unedited quotes like I do here, but in order to avoid confusion Im quoting maxtorixs full post here, I just needed to make clear those three are actually the precise same errors that Im getting!
So his is actually precisely the same error than my t-13 error, sorry for not describing it correctly.
Thanks maxtorix for confirming!
However, installing with WinNTSetup still provided me with the same errors during gui install:
T-16: Windows cannot load the Internet Configuration Library. The following error occurred: The specific module couldn't be found.
T-13: Cant access the actual required device, path or file
After final reboot: Your current security setting don't let this file to get downloaded.
The system then hangs on the Please screen.
Im very thinking about other peoples reports, did everybody use CD-based installs?
Windows cannot access the desired device, path or file. You may noy have appropriate persmissions to reach the item.
Posted: Sat Jun 07, 2014 11:20 pm Post subject:
Can either of yourself, Atari800xl or maxtorix, give a copy of your respective and files to help you harkaz system?
Posted: Sat Jun 07, 2014 11:22 pm Post subject:
Nope, no feature installed nor not installing, only the way it truly is.
Sp4 integrated to Dell ISO, has sp3
No programs installed, no features added with/without nlight, no features disabled with/without nlight.
Just think that torrenting sp1 of or windows 7 pro to sp4 to determine if that works out. Just wish my sp1 home edition cd worked only to test that theory out.
Ps. Yes idid reinstall and failed with this same error
Posted: Sat Jun 07, 2014 11:34 pm Post subject:
AHHHH! You mean you've an OEM Dell ISO that already includes SP3 along with other apps, you integrated SP4 compared to that ISO, then installed it to your clean partition? Or do you try to keep track of existing XP system with SP4 that you simply had previously used your Dell ISO to set up from? If neither of such was everything you did, then please explain in greater detail exactly which ISO you used and the way you got Sony Vegas installed even if this doesnt be effective. And since Im not mindful of an official Dell ISO that provide Sony Vegas Pro upon it, am I correct that this is just not an official ISO right from Dell? Or have I completely misunderstood everything you are saying?
Posted: Sun Jun 08, 2014 12:15 am Post subject:
2005 after we got this pc, few yrs later, 2009 ithink we'd a bad virus, I tried logging on looking to the default system, parrently it was required to been some stupid partition I guess which it had for being used just once by pressn f9 or somthing then it erases after with it once, witch is BS, so heres the not so good part, the yr before that, we'd a tech guy fix our pc on one occasion and made it pro from media center 2005, I tried, waisted months lookn due to this partition witch did exist at on one occasion. No disk came on this system. So later I developed a copy on the hard drive to another disk drive and been using the 2nd hard disk drive since. We hated Dell a lot bc it absolutely was always slower than hell with the stuff we had about it and couldnt wait. Until my pal screwed somthing very badly on the first hard drive that u cant do much while using system forget about like cant move files but in a position to copy files on the hard drive to a new usb drive.
Sometime last yr, since finishing my build, I put my hard disk drive on lockdown state and added that original disk drive on my top SATA spot, believe this or otherwise, this drive stood a humongous number of viruses onto it, used the best in the best with 4 other virus, security programs, 165-173 viruss.
Ino, pretty bad, we continue to have no idea what he did.
But why isnt msn sp3 broken then? Can ya answer that?
Posted: Sun Jun 08, 2014 12:54 am Post subject:
Can either individuals, Atari800xl or maxtorix, offer a copy of your respective and files that can help harkaz system?
Yes, already did that earlier.
And just in case this is getting confusing: Im using 100% original XPSP3-ENU MSDN hashes correct. Using WinNTSetup to fit.
Anthony21, please remove that large image out of your message, its getting tough to read the
Posted: Sun Jun 08, 2014 3:03 am Post subject:
Sry bout tat Atari, I thought I took it down n just gave link secs after I left fr work. Ill try with all the msn again, if it truely does work this time, I mightve redone personal files I already did by mistake.
Posted: Sun Jun 08, 2014 3:57 am Post subject:
Atarti800xL: Please retry minus the DPs. The driver for Intel Graphics and Chipset just isn't recognised as digitally signed.
Posted: Sun Jun 08, 2014 4:02 am Post subject:
I view you are still enhancing your pack, harkaz, good.
Ive finally done a whole new version, 1 year later, of windows 7. Perhaps this forum will be interested in your method harkaz, installing your skills for xp. The respectable members must already know just it anyway, to know. If you need something, you understand where to find me.
Posted: Sun Jun 08, 2014 5:18 am Post subject:
Atarti800xL: Please retry minus the DPs. The driver for Intel Graphics and Chipset just isn't recognised as digitally signed.
Testing at this time, if I get results quickly enough, Ill edit this message, otherwise Ill create a fresh one.
DriverPacks 10.06 is in fact only useful for Driver Pack Mass Storage 12.09, additional ones hp nc6320 drivers for video, audio, card reader, fingerprint sensor and modem, are added via WinNTSetup integration.
The difference is just not very imortant, but at the least its easy that i can test minus the conflicting? video driver, while leaving the required Mass Storage drivers intact.
I do wonder why the unsigned drivers can be a problem? They never were before, in theres even:
Thanks again to Harkaz youre really exceeding beyond and boyond for this one!! and all others.
Internet Connection Wizard - Windows cannot load the Internet Configuration library. The following error occurred: The specified module cannot be found.
Windows cannot access the actual required device, path, or file. You may not develop the approptiate permissions to get into the item.
EDIT3: Even removing not using any with the extra drivers doesnt help.
So which is: Using only the Mass Storage drivers, and not the nc6320-specific drivers. Same errors. This is as clean mainly because it gets in my opinion.
Posted: Sun Jun 08, 2014 10:16 am Post subject:
OK, Atari800xl, Im working within the issue with the moment, in addition to some other problems in custom setup.
The WinNTSetup is -based so I ought to emulate this somehow.
Posted: Sun Jun 08, 2014 12:53 pm Post subject:
POLL: Would you Framework 4.0 to get a non-default component in CD-ROM installation likewise?
FW 4.0 could cause boot delay and it is responsible for a 2-minute delay of OOBE.
Posted: Sun Jun 08, 2014 1:21 pm Post subject:
I dont currently possess a situation that will require CD install so I cant comment with that. But 4.0, my is that 4.0 installation becomes a possibility, in any in the installation scenarios, that ngen must be automatically executed 4.0 is installed. If you want or 4.0 and you really are willing to put up together with the longer install time it requires, then I would think that you simply would be happy to exchange slightly longer install time for quicker boot times there after. Just my two cents.
Posted: Sun Jun 08, 2014 1:23 pm Post subject:
FW 4.0 installs rather fast with no NGEN FW 3.5 takes about 10 minutes to fit.
Posted: Sun Jun 08, 2014 1:33 pm Post subject:
Maybe I was confused. I was talking about your statement above:
xvii In Framework 4.0 installer isn't going to run the executequeueditems command. This command is executed in OPWXPUP - it could increase installation time - but improves system boot time. To improve system boot quantity of USP4, you need to execute this command Framework 4.0 is completed along with your computer continues to be restarted.
Posted: Sun Jun 08, 2014 1:40 pm Post subject:
Typo - my mistake, I should correct it
Posted: Sun Jun 08, 2014 2:41 pm Post subject:
i dont mind which has a 2-minute delay of OOBE, saves me a little while getting it and setting it up. in my opinion, its worth the cost, defiantly when it involves completely finished sp4, Just think of it as a still part from the blue setup which you have to wait est 39mins or less depending what pc ur using.
do somthing else while its installing for that last est. 15mins or so
Posted: Sun Jun 08, 2014 3:05 pm Post subject:
I think you misunderstood my suggestion.
xvii In Framework 4.0 installer doesn't run the executequeueditems command. This command is executed in OPWXPUP - it will increase installation period in OPWXPUP - but improves system boot time. To improve system boot in time USP4, you must execute this command Framework 4.0 is completed and also your computer continues to be restarted.
I believe SP4s behavior must be like OPWXUP in cases like this. 4.0 is installed, then I imagine that ngen should be cost take advantage in the resulting reduction in boot period in all future boots. The increase in install time seems for being an acceptable trade-off. But that is certainly just my.
Posted: Sun Jun 08, 2014 3:36 pm Post subject:
bphlpt I had tried this inside past, nevertheless it can create problems. For this reason I decided not to ever include this command. It could be run at runonce but this may happen whenever you reinstall it from OC Manager plus it will demonstrate a blank desktop for around 20
Posted: Sun Jun 08, 2014 6:22 pm Post subject:
Oh. OK I guess that could be a problem.
Posted: Mon Jun 09, 2014 10:01 am Post subject:
All my previous tests were stated in Windows 7 x64. I did countless integrates of OnePieceWindowsXPPost-SP3UpdatePack with nLite and RVMi in Windows 7 x64 without issues. Seems that only nLite can correctly slipstream this SP4 in Win 7. The CMD had the problem together with the key not accepted as valid. I do not know why. What nLite can do plus the direct CMD dont manage in Win 7 as I run the command as admin? The process seems to become simmilar in progress although not the outcome.
Anyway, I installed a clean SP3 in VMWare boost it from WU to the most up-to-date available so I could run quality slipstreams in VM.
These are examination images made in various scenarios.
As you may see the CMD and nLite images are same in space apart from your RVMi created image in the nLite slipstreamed. RVMi ads his boot image from the root. However this RVMi created image works without problem. So the issue isnt for the image creation.
But the RVMi splipsteamed image has a similar problem as my previous post. As you are able to see the style is smaller. There are missing files.
1. WIN51CD2 - this Im not certain that will cause that problem
2. - this sure could cause that problem
Now, I watched the full process. With CMD and nLite I get a final prompt saying succesfully slipstreamed like thing. Not with RVMi.
As it seems first stage is extraction, than integration and prior to the end it's like it starts again a bit integrate, this may very well be a cleanup thing, I guess. This happens regardles with the items method can be used but appears as if at this stage RVMi removes those files. I don't realize why. I watched the folder content during this period
nLite - Windows XP and Windows 7 x64 no problems.
Now comes the tricky part. I did each of the install tests in VM from ISO and USB manufactured by WinSetupFromUSB, I cant seem to deal with to create an USB together with the WinNTSetup everyone talk about, a link with a guide would help
Installs from USB have clean Event Viewer, clean and no unsigned in Hooray. Congrats! Good JOB!
Windows Setup encountered non-fatal errors during installation. Please check the obtained in your Windows directory for additional information.
Contact your whole body administrator, who may provide assistance in diagnosing this concern.
Posted: Mon Jun 09, 2014 11:39 am Post subject:
ianymaty Can you send me the file? It will show me which command didn't execute.
Posted: Mon Jun 09, 2014 11:52 am Post subject:
Oh, I didnt saved them as I did all of the installs, just looked from it for unsigned files because you asked.
Ill do another install and post it.
Just droped if you ask me a box and today I have possibility to see a live install from USB.
Posted: Wed Jun 04, 2014 9:44 pm Post subject:
has for being a 32bit environment since 64 doesnt use a sp3.
Light blue screen to keep the SetUp, before it shows anything apart from the mouse, system reboots and trys again with continue the setuplight blue. in a very loop.
whats the/integrate switch?
Posted: Thu Jun 05, 2014 8:25 am Post subject:
has to become a 32bit environment since 64 doesnt employ a sp3.
whats the/integrate switch?
I mean: does one run nLite inside a Windows XP x86 environment? Not the CPU architecture on the SP3 media you might be modifying.
The proven fact that SP4 slipstreamed media just isn't recognised by nLite means that this integration is problematic.
To slipstream, run the command/integrate:C:XPPRO where c:xppro can be a folder made up of the extracted items in SP3 ISO.
Posted: Thu Jun 05, 2014 8:59 am Post subject:
Currently taking care of an patch - wanting to fix conditions that occur when reinstalling SP4 live installer after its prior uninstallation.
Posted: Thu Jun 05, 2014 1:27 pm Post subject:
thx, that defiantly worked.
I mightve mist this n forgot only mentioned it already all of C KB2538243 n silverlight.
Location: Victorville, California
Posted: Thu Jun 05, 2014 3:15 pm Post subject:
Just somewhat of a reminder - if your user burns with a DVD everything will fit - the 700Mb barrier doesn't exist. I would think everyone today burns to DVDs anyway.
Posted: Thu Jun 05, 2014 7:43 pm Post subject:
Anthony21 No, C runtime and Silverlight wont be contained in this Service Pack.
I re-patched the file and added some additional uninstall commands to repair the aformentioned issues. Everything seems ok at the moment. Reinstallation after uninstallation runs perfectly. In addition, some post-uninstallation registry errors have disappeared when I applied the newest patches about 20 modifications to were required.
Compiling the sfxcab - its contents are timestamped with the first period in XP SP4 developement. This means we have been close towards the stable release.
After publishing the Beta2 build, possibly tomorrow, I will start writing the production notes and documentation. Windows XP SP4 RC would include them, likewise as any necessary fixes.
Please help make your suggestions on the should be contained in the SP4 documentation.
Posted: Thu Jun 05, 2014 10:51 pm Post subject:
harkaz, you've absolutely done a fantastic job for this project. You must be heartily congratulated!
You appear to have done an exceptionally thorough job in testing all various installation methods including CD, DVD, USB, live install, integrate then install, reinstallation after uninstallation, etc, so I would significantly appreciate your comments with regards to a matter that Atari800xl has taken up. It appears as if SP4 and some on the other XP update packs sometimes produce an issue whenever you try to utilize WinNTSetup, which is usually a very respected tool and it is able to be employed to do installs for XP, Win7, Win8, etc. JFX believes that WinNTSetup is okay, and hubby has no current intentions to modify it to end the conflict since XP is EOS. He also believes which the problem lies either inside the update packs themselves and/or the tools utilized to integrate them for instance nLite or RVMi. Since you've got tested investing in SP4 by numerous different methods, both with and without external tools, I use a hard time believing that this fault with WinNTSetup is using either SP4 or perhaps external tool. BUT, if there was clearly something that may very well be added to SP4 to alleviate the difficulty with WinNTSetup, without interfering together with the proper operation of SP4 rolling around in its other methods of integration, that will really be great. Those same forms of changes maybe might also then be applied to additional packs. On additional hand, when you could help know very well what change will be required in WinNTSetup to permit its successful use with SP4 and hopefully the opposite update packs at the same time, then perhaps JFX might be persuaded to produce a change of course. In order to have that to occur Im sure this kind of change would have to become such that however not need to help keep tweaking it everytime an latest version of one from the update packs is released.
Anyway, I would thank you for thoughts.
Posted: Fri Jun 06, 2014 2:06 am Post subject:
bphlpt I have incorporated many changes in the most recent build, which seems to repair the WinNtSetup issues. I have changed double-refernces so how the files are moved properly to/i two different folders. For example, there are 2 file: and iedkcs32.m00 that happen to be actually precisely the same file but referenced using a different name and copied to folders.
In addition the file will not be copied during GUI-mode setup but its positioned in catalog root and copied into a folders when XPSSVCS OC is set up on T-27 setup phase. This wasnt true within the previous release.
Posted: Fri Jun 06, 2014 2:13 am Post subject:
Thank you a lot bphlpt on your well-worded request, and thanks a lot harkaz when planning on taking the extra trouble of having everything to use WinNTSetup, I really didnt expect that!! Im very excited to find out any new
It would likely be so very very useful to add XPSP4 into a WinPESE8 USB, as Ive said before this is really a very easy way of needing the install files of w7-32/64, w8.1-32/64, xp with POSReady updates/without, etc. etc. all on a single USB!
Posted: Fri Jun 06, 2014 10:16 am Post subject:
Windows XP SP4 Unofficial Beta 2 Build is actually available!
This relieve Windows XP SP4 Unofficial is actually stable.
All known bugs are actually fixed on this version. No documentation is roofed yet.
This version includes ALL Windows XP updates and a lot of updated components with all of their latest updates around including May 2014 POSReady updates included.
Frameworks 1.0, 1.1, 2.0, 3.0, 3.5, 4.0, MSXML40 SP3, Adobe Flash Player 13 May 2014, IE8, WMP11, Bitlocker to travel reader, XPS Viewer EP, Windows Search 4.0 disabled automagically, IMAPIv2, Remote Desktop Connection Client 7.0, exFat update, Windows Installer 4.5, QFECheck tool, WGA notifications disabled automagically, Windows Feature Pack for Storage 1.0, November 2013 Revoked roots and Root cerificates, Windows Rights Management Client, DirectX 9.0c June 2010 Update, DirectX for Managed code included Framework 3.5, WebDAV update for Office 12 Rosebud.
Windows Powershell will not be included. It is usually installed seperately FW 3.5 gets installed.
KB898461 - Software update 898461 installs an enduring copy with the Package Installer for Windows version 6.1.22.4
KB916157 v6 - When you obtain a Stop error message or perhaps a fatal system error message, a user-mode process dump file just isn't created in Windows XP
KB927436 v2 - Error message once you attach a device that loads the driver with a computer that is certainly running Windows XP SP2, Windows XP SP3, or Windows Server 2003: DRIVERVERIFIERIOMANAGERVIOLATION c9
KB932716 v2 - Description in the Image Mastering API v2.0 IMAPIv2.0 update package that is certainly dated June 26, 2007
KB934401 - When you run the Ipconfig/displaydns command in Windows Server 2003, the outcomes are incomplete
KB942288 v3 - Windows Installer 4.5 is available
KB946648 - MS08-050: Description on the update for Windows Messenger 4.7 for Windows XP : August 12, 2008
KB948698 - You cannot makes use of the utility to get into 64-bit registry keys on the 64-bit computer coming from a computer that's running a 32-bit version of Windows Server 2003, Windows XP, Windows Server 2008, or Windows Vista
KB948877 v2 - After you copy multiple files from your computer that may be running Windows XP with a PCMCIA SRAM card, a number of files within the card are corrupted
KB950820 - The system stops responding throughout the logoff, shutdown, or restart process on the computer which is running Windows Server 2003 or Windows XP and that contains the Japanese IME installed
KB950982 - A listing of ODBC system DSNs is truncated if your total number of characters that happen to be used in the many DSN names is a bit more than 7, 500 using a computer that's running Windows XP or Windows Server 2003 SP2
KB951163 - When you try make use of the MSTSC command from Terminal Services Client 6.0 to connect on the local Windows XP - based computer, a black screen can take place for several minutes
KB951618 v2 - A black screen issue occurs with a Windows Vista-based computer or maybe a Windows XP Service Pack 2-based computer containing Onekey Recovery 5.0 installed once you upgrade the operating system
KB951822 v2 - You receive one message, paper operation fails, or partial pages are printed when you seek to print into a Citizen printer as well as to an Alps printer in Windows XP Service Pack 3
KB951978 - Script output just isn't displayed as expected once you run VBScript or JScript scripts in Windows Vista Service Pack 1, in Windows Server 2008, or even in Windows XP Service Pack 3
KB952117 v2 - When you attempt to put a Windows XP - based computer into hibernation or into standby, the pc stops responding
KB953028 - On a computer that is certainly running Windows Server 2003 or Windows XP, a credit application experiences an access violation and crashes in the event the computer has over four cores or greater than four logical processors
KB954193 - Description with the Jet 4.0 Database Engine cumulative hotfix package for Windows XP SP2 and SP3, Windows Server 2003 SP1 and SP2, Windows Vista, Windows Vista SP1, and Windows Server 2008: July 2, 2008
KB954434 - A multiprocessor computer that is certainly running a Windows XP, Windows Server 2003, or Windows Vista stops responding using a black screen when you finally resume the pc from hibernation
KB954920 v2 - When a software requests a consequence set from new SQL Server 2008 collations, you could possibly receive an MSG 40242 or MSG 40205 error once the ODBC driver for SQL Server is utilized or an MSG 40234 error if your SQL OLE DB provider can be used
KB955356 - When you seek to start a Windows XP SP3-based computer that's connected to an outside IEEE 1394 hard drive, the computer may stop responding ahead of the logon screen appears
KB955576 - TAPI-based applications stop responding, and you also cannot disconnect telephone calls using a Windows XP - based telephony server
KB955830 v2 - When you connect to some Windows XP - based computer using a remote desktop connection, laptop computer may be not competent to automatically enter in the Sleep mode again when you finally log off laptop
KB955988 - The Win32Environment WMI class isn't going to return the value with the PATH environment variable when the variable consists of in excess of 1, 024 characters with a Windows XP - based computer
KB957502 - Error message when you make an effort to open some MMC 3.0 snap-ins inside a localized version of Windows XP Service Pack 3: MMC can't create the snap-in. The snap-in might not happen to be installed correctly.
KB957931 - A Windows XP - based, Windows Vista-based, or Windows Server 2008-based computer isn't going to respond to 802.1X authentication requests for 20 minutes from a failed authentication
KB958910 - When you send a print job to a Internet Printer Protocol IPP print server coming from a Windows - based computer, paper job fails and not restarts
KB959267 - After you repeatedly dock and undock a Windows XP - based portable computer that may be connected with a docking station, you could possibly be struggling to change the state associated with an attached network device
KB959465 - Write protection isn't going to always focus on SD memory cards which are plugged in a computer that runs Windows XP, Windows Vista, or Windows Server 2008
KB959682 - FIX: A Message Queuing 3.0 message is rejected about the receiver whenever you send the material by using another certificate from the Windows XP Service Pack 3-based computer