harkaz
Content Type
Profiles
Forums
Events
Posts posted by harkaz
-
-
Currently building .NET Framework 3.5 uninstaller. I will have to modify .NET Framework 1.1 uninstaller as well.
Preparing the .NET uninstaller will take enough time.
After that, I'll have to enable .NET Framework 3.5 live installation/uninstallation which will take even more time....
0 -
If you can get your hands on a evaluation key. (Not product key) you can use POSReady 2009 for a full year before shutdown. Also Keys dont expire after use.
Yes, it won't be recognised by nLite.
Why would you need to. It already is very minimalist.
I have already found an OEM product key for POSReady 2009. I have been trying to find a way to convert a normal XP Pro installation to Embedded so that the Windows Update of a normal XP Pro machine would show POSReady updates without having to install Windows POSReady from scratch.
It seems that Embedded versions contain some extra files required to boot Windows properly. I have no idea which those files are. After all, it seems much easier to port any future updates manually from POSReady 2009 to normal Windows XP editions.
Does it have a timer of death.
The eval product key has a timebomb while the OEM product key doesn't. Once you enter an OEM product key during POSReady 2009 setup it's activated forever.
0 -
If you can get your hands on a evaluation key. (Not product key) you can use POSReady 2009 for a full year before shutdown. Also Keys dont expire after use.
Yes, it won't be recognised by nLite.
Why would you need to. It already is very minimalist.
I have already found an OEM product key for POSReady 2009. I have been trying to find a way to convert a normal XP Pro installation to Embedded so that the Windows Update of a normal XP Pro machine would show POSReady updates without having to install Windows POSReady from scratch.
It seems that Embedded versions contain some extra files required to boot Windows properly. I have no idea which those files are. After all, it seems much easier to port any future updates manually from POSReady 2009 to normal Windows XP editions.
0 -
I tried again by modifying Windows xp text-mode registry INF files. Again, system could not start at first boot (clean instalation initiated with the ProductSuite value set to "EmbeddedNT") - with a difference: it performed automatic restarts. Booting in debugging mode did not show any BSODs however.
I will try to remove the ProductSuite value from Windows Embedded to see what happens.
UPDATE: When I remove the productSuite value in POSReady 2009, winlogon starts and shows Windows Professional logo. But when I try to logon, it shows "A problem is preventing Windows from accurately checking the license for this computer. Error code: 0x8007074e "
0 -
@vinifera The two winlogon.exe file are identical: they have the same MD5 and SHA-1 hashes.
It must be a kernel exception that causes this failure.
0 -
Windows XP Embedded is recognised by the:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\ProductOptions\ProductSuite key value.
It must be set to EmbeddedNT.
I have tried to change the value by modifying hive offline but winlogon failed to start.
Has anyone managed to overcome this before?
0 -
Yes, it won't be recognised by nLite.
0 -
HKLM\SYSTEM\WPA\POSReady, Installed DWORD value set to 1 seems to be an important key for POSReady detection.
I will check the key you mention as well.
0 -
It would be nice if we would trick Windows Update into "thinking" that normal Windows XP Professional is Windows Embedded POSReady 2009.
I had found a registry key which is checked by Embedded-specific updates to ensure that Windows Embedded is used, but I can't recall it at the moment.
0 -
no
vista is trash to me
That's your opinion. I liked Vista, but not everyone did.
yup
thats why I wrote "to me"
on the sidenote, there is always deiscussion on POS ready 2009
but did anyone tried it personally ?
is its kernel 5.1 or 5.2 ?
a) OS Version number
Original version number: 5.1.2600.5512 (Service Pack: 3)
Latest version number (April 2014): 5.1.2600.6532 (Service Pack: 3)
B) Windows PE version number is 5.2.3790.1830 (Windows Server 2003 SP1 - WinPE 2005)
Let's see if the upcoming POSReady 2009 updates will be the same as those distributed in Windows XP custom support.
0 -
@usmangujjar Yes, you can slipstream SP4 into your Windows XP installation dmedia and then burn it to CDs/DVD/USB using the appropriate tools.
I don't know exactly when the final release will be ready, because .NET Framework 3.5 integration - which I'm currently working on - is rather hard, even if Onepiece has already done most of the work for me.
0 -
@Acheron Thanks for publishing the patches in one place. It's not easy to develop these patches without help...
1 -
The Alpha 2 build is being uploaded at the moment.
UPDATE: Windows XP SP4 Alpha 2 is available at RyanVM.net.
0 -
And while I'm testing the Windows XP SP4 Alpha 2 Build, which fixes the Kabul Time Zone syndrome but adds no new updates/features to the SP4 package (for the moment), I thought about performing a "weird" test that would show me whether POSReady 2009's post-April 2014 updates would need special porting to run on Windows XP.
Simply put, I ran Windows XP SP4 Alpha 2 installer on top of Windows POSReady 2009.
The result? Well, pictures speak louder than words...
1 -
I'm fixing a couple of bugs in the SP4 Alpha version. One of them is the Kabul Time Zone Syndrome": in CD-ROM installations, you always get Kabul as the selected time zone no matter what you choose.
I have narrowed down the cause of this issue, so expect an Alpha 2 release very soon..
By the way, I got my hands on Windows Embedded POSReady 2009. It is Windows XP SP3 and it will be supported until 2019. In Windows Embedded POSReady 2009 Service Pack 3 I could find almost everything present in the Windows XP SP3 package. Even the \ic folder was there (is there a "Home/Personal" version of WEPOS that I don't know?).
There are only a few binaries different in XP Home and Professional, as one sees in the service pack: dpcdll.dll and pidgen.dll. Dpcdll.dll is the only one which has been affected by updates (winlgon.exe updates I think affect this one).
As for the INF files, I can do everything I want with them and nothing at all will complain.
It's highly likely, after all, that April 2014 won't be the end for Windows XP x86...
0 -
Which tool are you using, sfxcab?
This article says that you can extract IPD-compressed files using extract.exe found in Vista OPK:
http://technet.microsoft.com/en-us/library/cc722332(v=ws.10).aspx
0 -
@ vinifera: I plan to include all updated Windows components in the SP4. Microsoft .NET Frameworks are removable components in this Unofficial Service Pack 4, the same goes for XPS Viewer and Windows Search 4.0. .NET Frameworks and XPS Viewer enabled by default, however, while Windows Search 4.0 is disabled by default. Media Center and Tablet PC are installed only when Windows XP SP4 is installed/slipstreamed in MCE/Tablet PC system or installation disk, respectively.
0 -
Welcome to Windows XP Service Pack 4 (Unofficial).
Windows XP SP4 (Service Pack 4) is a cumulative update rollup for Windows XP.Windows XP SP4 Final is now available!
Windows XP SP4 can installed on any version of Windows XP with SP1 or later installed or slipstreamed into any Windows XP installation source (except for Embedded versions). It includes all updated components and hotfixes for Windows XP in a single, convenient package. Except for the SP4 package installer main executable (update.exe) and a cosmetic resource modification sysdm.cpl no other binary file has been modified, everything is original from Microsoft Corporation.
Microsoft .NET Frameworks 4.0, 3.5, 1.1, 1.0 are included in this package. .NET Framework 1.0 will be installed only with Tablet PC Edition or Media Center Edition (Upgrade only). .NET Framework 4.0 is disabled by default.
It's possible to split the slipstreamed installation source into two 650 MB CD-ROMs, which can be essential for older computers. You can also create 6 Bootable Floppy Disks to install Windows XP on older systems which cannot boot from CD-ROM.Furthermore, Windows XP SP4 includes security enhancements that address issues not fixed by Microsoft Updates. It also includes performance tweaks that should make your PC run blazingly fast.
NOTE: Before installing SP4 on a system with many post-SP3 updates installed, follow the steps described here (do not restart your PC after applying these steps, just run the SP4 installer and then reboot):
http://www.rarst.net/software/failed-install-catalog-files/
This will prevent a common error message: "Failed to install catalog files"
Although SP4 installer takes steps to automatically delete these files, it may require manual intervention in some cases.
Download at official Internet Archive repo: https://archive.org/details/xp-unofficial-sp4-jan2022_20220113
View contents of ryanvm-archive-xpsp4-posts.7z on the Internet Archive download location for additional information. (Current version: Version 3.1b Released on 08 March 2016 23:00:00 UTC).
Enjoy Windows XP Service Pack 4.1 - UPDATE [June 7, 2019]: Post-SP4 Update Pack released!
This final update pack should be applied to Windows XP installation media immediately after slipstreaming SP4 v3.1b to a Windows XP RTM/SP1/SP2/SP3 source. This will update installation media to May 2019, including every single update released until the POSReady 2009 end-of-life in May 2019. Download available at RyanVM.net.2 - UPDATE - 15 OCT 2018:
For novice users that do not want to wait for 20-30 minutes after installing XP SP4 AND rebooting
For all .NET haters...
A NEW RELEASE OF UNOFFICIAL SP4 3.1B WITHOUT .NET FRAMEWORK
This release will not install .NET Framework in both live and slipstreamed install, unless:
- Media Center Edition is used -> .NET Framework 1.1 SP1 is installed
- Tablet PC Edition is used -> .NET Framework 1.0 SP3 is installed
Users can still install .NET FWs of their choice from the Add/Remove Components wizard in Control Panel
This alternative SP4 release is called:
WindowsXP-USP4-v3.1b-NODOTNET-x86-ENU.exe
In addition, XP SP4 OEM Preinstallation Kit ISOs with SCSI drivers, and an updated MUI ISO have been released!3 - IMPORTANT NOTICE FOR XP SP4 USERS [08/03/2016]: Microsoft has changed its WU update detection strategy. The following key must be removed to continue receiving automatic updates from WU:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WindowsEmbedded
Use the sp4_march16_wufix.reg found inside the respective zip file at my Google Drive in order to automate the process. Version 3.1a users don't need to do anything more than that.
A new v3.1b version has been released with this change, just for new installs. No other updates have been added.
3 -
Hi nuhi
For the last few months, I've been working on Windows XP SP4 - a cumulative update rollup for Windows XP Home, Pro, MCE, Tablet PC, K, KN, N, Starter, which works similarly to XP SP3 installer. I'm now testing the alpha build, which I'm going to publish very soon.
I've noticed that after slipstreaming SP4 to an XP source, nLite will crash:
I suspect that the cause of this crash is the fact that XP SP4 references two CD-ROMs in its layout.inf/txtsetup.sif files.
I hope that you can look into this after I've finished XP SP4 Alpha.
You can find more info about the project here: http://www.ryanvm.net/forum/viewtopic.php?t=10321
I may also create a new thread here in MSFN so that more testers can take a look at the XP SP4 package.
0 -
The first argument is a special folder code. Below you can find the special folder codes:
const int CSIDL_DESKTOP = 0x0000; // <desktop>
const int CSIDL_INTERNET = 0x0001; // Internet Explorer (icon on desktop)
const int CSIDL_PROGRAMS = 0x0002; // Start Menu\Programs
const int CSIDL_CONTROLS = 0x0003; // My Computer\Control Panel
const int CSIDL_PRINTERS = 0x0004; // My Computer\Printers
const int CSIDL_PERSONAL = 0x0005; // My Documents
const int CSIDL_FAVORITES = 0x0006; // <user name>\Favorites
const int CSIDL_STARTUP = 0x0007; // Start Menu\Programs\Startup
const int CSIDL_RECENT = 0x0008; // <user name>\Recent
const int CSIDL_SENDTO = 0x0009; // <user name>\SendTo
const int CSIDL_BITBUCKET = 0x000a; // <desktop>\Recycle Bin
const int CSIDL_STARTMENU = 0x000b; // <user name>\Start Menu
const int CSIDL_MYDOCUMENTS = CSIDL_PERSONAL; // Personal was just a silly name for My Documents
const int CSIDL_MYMUSIC = 0x000d; // "My Music" folder
const int CSIDL_MYVIDEO = 0x000e; // "My Videos" folder
const int CSIDL_DESKTOPDIRECTORY = 0x0010; // <user name>\Desktop
const int CSIDL_DRIVES = 0x0011; // My Computer
const int CSIDL_NETWORK = 0x0012; // Network Neighborhood (My Network Places)
const int CSIDL_NETHOOD = 0x0013; // <user name>\nethood
const int CSIDL_FONTS = 0x0014; // windows\fonts
const int CSIDL_TEMPLATES = 0x0015;
const int CSIDL_COMMON_STARTMENU = 0x0016; // All Users\Start Menu
const int CSIDL_COMMON_PROGRAMS = 0x0017; // All Users\Start Menu\Programs
const int CSIDL_COMMON_STARTUP = 0x0018; // All Users\Startup
const int CSIDL_COMMON_DESKTOPDIRECTORY = 0x0019; // All Users\Desktop
const int CSIDL_APPDATA = 0x001a; // <user name>\Application Data
const int CSIDL_PRINTHOOD = 0x001b; // <user name>\PrintHood
const int CSIDL_LOCAL_APPDATA = 0x001c; // <user name>\Local Settings\Applicaiton Data (non roaming)
const int CSIDL_ALTSTARTUP = 0x001d; // non localized startup
const int CSIDL_COMMON_ALTSTARTUP = 0x001e; // non localized common startup
const int CSIDL_COMMON_FAVORITES = 0x001f;
const int CSIDL_INTERNET_CACHE = 0x0020;
const int CSIDL_COOKIES = 0x0021;
const int CSIDL_HISTORY = 0x0022;
const int CSIDL_COMMON_APPDATA = 0x0023; // All Users\Application Data
const int CSIDL_WINDOWS = 0x0024; // GetWindowsDirectory()
const int CSIDL_SYSTEM = 0x0025; // GetSystemDirectory()
const int CSIDL_PROGRAM_FILES = 0x0026; // C:\Program Files
const int CSIDL_MYPICTURES = 0x0027; // C:\Program Files\My Pictures
const int CSIDL_PROFILE = 0x0028; // USERPROFILE
const int CSIDL_SYSTEMX86 = 0x0029; // x86 system directory on RISC
const int CSIDL_PROGRAM_FILESX86 = 0x002a; // x86 C:\Program Files on RISC
const int CSIDL_PROGRAM_FILES_COMMON = 0x002b; // C:\Program Files\Common
const int CSIDL_PROGRAM_FILES_COMMONX86 = 0x002c; // x86 Program Files\Common on RISC
const int CSIDL_COMMON_TEMPLATES = 0x002d; // All Users\Templates
const int CSIDL_COMMON_DOCUMENTS = 0x002e; // All Users\Documents
const int CSIDL_COMMON_ADMINTOOLS = 0x002f; // All Users\Start Menu\Programs\Administrative Tools
const int CSIDL_ADMINTOOLS = 0x0030; // <user name>\Start Menu\Programs\Administrative Tools
const int CSIDL_CONNECTIONS = 0x0031; // Network and Dial-up Connections
const int CSIDL_COMMON_MUSIC = 0x0035; // All Users\My Music
const int CSIDL_COMMON_PICTURES = 0x0036; // All Users\My Pictures
const int CSIDL_COMMON_VIDEO = 0x0037; // All Users\My Video
const int CSIDL_RESOURCES = 0x0038; // Resource Direcotry
const int CSIDL_RESOURCES_LOCALIZED = 0x0039; // Localized Resource Direcotry
const int CSIDL_COMMON_OEM_LINKS = 0x003a; // Links to All Users OEM specific apps
const int CSIDL_CDBURN_AREA = 0x003b; // USERPROFILE\Local Settings\Application Data\Microsoft\CD Burning
const int CSIDL_COMPUTERSNEARME = 0x003d; // Computers Near Me (computered from Workgroup membership)
const int CSIDL_FLAG_CREATE = 0x8000; // combine with CSIDL_ value to force folder creation in SHGetFolderPath()
const int CSIDL_FLAG_DONT_VERIFY = 0x4000; // combine with CSIDL_ value to return an unverified folder path
const int CSIDL_FLAG_DONT_UNEXPAND = 0x2000; // combine with CSIDL_ value to avoid unexpanding environment variables
const int CSIDL_FLAG_NO_ALIAS = 0x1000; // combine with CSIDL_ value to insure non-alias versions of the pidl
const int CSIDL_FLAG_PER_USER_INIT = 0x0800; // combine with CSIDL_ value to indicate per-user init (eg. upgrade)The second argument is a string with the name of the special folder's subfolder where you will save the link to. Leave this argument blank (put a comma) if you want to save the link in the special folder you specified.
The third argument is the command the shortcut will execute.
The fourth argument specifies a dll file with the shortcut's icon.
The fifth argument species the icon index in the specified dll
The next 3 arguments are unknown.
The 9th argument seems to be the target path of the shortcut.
10th, 11th arguments probably specify the dll with a specified string resource to show in shortcut's description.
0 -
1. Grab the original XP SP3 syssetup.dll file.
2. Using a hex editor, like XVI32, open the dll file.
3. Go to address (offset) 33B7B.
4. Replace 74 with EB.
5. Save changes to syssetup.dll
6. Using modifype -c command or a similar tool fix the PE checksum.
7. To get rid of the "Battery unsigned" issue, you have to perform this additional step: Open the syssetup.inf with notepad. Go to the [DeviceInfsToInstall] section of the INF file. Delete or comment the line with the battery.inf file. Save changes.
8. Use the new syssetup.dll and syssetup.inf files instead of the original ones.Known side-effects: Setuperr.log file reports that syssetup.dll is not properly signed. In addition, SFC does not protect syssetup.dll after installing Windows. However, SFC does not report any problems after Windows installation.
0 -
Problem solved. Cause: ISO Emulation was problematic in Virtual Machine.
0 -
Hi there.
Yesterday I used Deployment Image Servicing and Management Tool (DISM) to add drivers to an untouched SP1-U x86 ISO from digital river. After that, Windows failed to start, because of driver corruption.
It had nothing to do with the specific drivers I integrated, I checked it with many drivers. In all cases, I was getting the same error message.
I am downloading a SP1 ISO (without the -U) to see if problems persist.Have you ever experienced a similar issue?
0 -
Windows Help and Support is updated online. How can one download those updated help files and register them, so that they are available to a computer without Internet access?
0
POSReady 2009 updates ported to Windows XP SP3 ENU
in Windows XP
Posted
Of course, there's a simpler version of it:
NOTE [08/03/2016]: All SP4 users up to including version 3.1a must delete the following key to continue receiving the latest updates automatically from WU:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WindowsEmbedded
Direct Links to WU/MU:
=================######=================
UPDATE [22/5/2014]: Sebijk reported that a simple registry tweak is enough for WU to show the latest POSReady updates on Windows XP. This method has been tested and works on any XP build.
Add the following registry keys (INF Format):
HKLM,"System\CurrentControlSet\Control\WindowsEmbedded\ProductVersion","FeaturePackVersion",0x00000000,"SP3"
HKLM,"SYSTEM\WPA\WEPOS","Installed",0x10001,0
HKLM,"SYSTEM\WPA\WES","Installed",0x10001,0
HKLM,"SYSTEM\WPA\POSReady","Installed",0x10001,1
and restart the computer. Then run WU to get the latest updates.
ORIGINAL METHOD:The latest Patch tuesday updates have been easily ported to a Windows XP virtual system - fully updated until April 2014.
The constraints are entirely artificial. Porting is easy as 1-2-3:
1. Modify update.inf file and remove the
condition=CompositeOp,OrOp,Prereq.XPInstallEmbedded.Section line
from the Prerequisite section.
2. Use a patched update.exe version 6.3.13.0 or later to accept the modified update.inf file. Update.exe files differ between various languages.
UPDATE: Instructions on how to apply the patch to any language can be found here:
http://www.msfn.org/board/topic/171814-posready-2009-updates-ported-to-windows-xp-sp3-enu/?p=1078363
3. Compress to SFX EXE file. Delta compression optional.
I have already uploaded the files at RyanVM.net...
So Windows XP can have semi-official support until 2019!