Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

33 Excellent

About harkaz

  • Rank
    Windows XP SP4 Developer

Profile Information

  • OS
    Windows 7 x64
  • Country
  1. Yes. But you won't need to do it after all, if you haven't experienced the issue with ntfs drives.
  2. OK, you will boot from Windows 7 X86 (32-BIT) installation DVD, and launch command line pressing SHIFT+F10. Get GIMAGEX binaries folder from: http://gimagex.windows10compatible.com/ and copy to external HDD. Then connect an external USB HDD/Flash with enough space to store you xp hdd data and the GIMAGEX BINARIES. Launch Gimagex x86 binary from the command line. Source: set to the drive letter of the xp hdd (not always, click Browse to make sure) Destination: points to your external hdd, where your snapshot will be saved (use Browse to specify dest. fodler and snapshot file name) Name/Description/Display Name/Display desc: XP Snapshot + date Click capture UPDATE: Set Compression to Maximum as well.
  3. Makes sence since _IEnumConnections_RemoteNext_Proxy, and _IEnumConnectionPoints_RemoteNext_Proxy are missing.
  4. First of all, let me clarify if you did experience the error messages when copying/opening files from your NTFS-formatted flash drive. Only if you did so, will I be able to assess the situation. To get a system image use GIMageX from a Windows PE (Vista+) environement - I prefer Windows 7 personally. To anyone with these issues, I need just one snapshot of the problematic state.
  5. I'm not sure if it is an issue of ntfs.sys or a regression issue. Has anyone with an SP4 system + latest updates experienced the issue? I need to exclude the possibility of other updates interfering. If you can take a snapshot of a system (if there are ntfs.sys problems) and upload it somewhere so I can test it, that would be great.
  6. @dencorso Works just fine.
  7. @dencorso Cannot reproduce it yet. I formatted the usb stick as NTFS on my Windows 10 host copied some files to it. Then I safely removed the drive from host, and replugged the usb stick to the host. Attached usb drive to VM. Successfully copied files to the disk in the XP VM. The same happens without prior safe removal.
  8. Can you PM me with some instructions? I'd like to know more details about the method. @everyone I need a reliable method to reproduce the ntfs.sys issues you faced. On the VM I use for debugging with the latest updates and SoftICE (XP SP4) the security descriptor errors do not occur. Just copied the entire Program Files dir to my flash drive. Next test will be with DEP enforced, to see if this has anything to do with it.
  9. Regarding ntfs.sys there are the following differences from the previous stable version (5.1.2600.5782) 1) NtfsSetupUsnJournal 2) A) B) C) The significance of these changes and the relevance with removable drives has to be analyzed with a kernel debugger later. I will also take a look at existing documentation.
  10. You're welcome. Actually there is one small patch that can be added to good old oleaut32.dll. We may need to add and debug a jmp above instruction (loop) to the good old file, so that it is jmp 0x77125785 below 0x77125788 I need somebody's help to rebuild the DLL however. Ntfs.sys is analyzed next.
  11. I have analyzed the buggy oleaut32.dll vs the latest stable version (5.1.2600.7248). The following functions are missing from the buggy file: Statistical analysis shows no other differences, consequently using the old oleaut32.dll seems to have no security impact whatsoever.
  12. Introducing - Unofficial Windows XP SP4

    I have tested it again, it's not working indeed due to an updated licensing DLL file not compatible with Embedded editions of Windows (not offered by Windows update to Embedded SKUs). So, yes USP4 is not compatible with POSReady 2009.
  13. Introducing - Unofficial Windows XP SP4

    The Microsoft Update has been problematic over the last months. Version 3.1a will not download the latest updates on my test machine. Version 3.1b has difficulties and always requires installing the latest IE cumulative update manually on my test machine, otherwise it is unable to detect updates properly. You can install it on POSReady 2009, yes.
  14. Latest Version of Software Running on XP

    MSI Error 1603: MSI (c) (30:60) [03:46:21:203]: Note: 1: 1708 MSI (c) (30:60) [03:46:21:203]: Product: Java 8 Update 161 -- Installation failed. MSI (c) (30:60) [03:46:21:203]: Windows Installer installed the product. Product Name: Java 8 Update 161. Product Version: 8.0.1610.12. Product Language: 1033. Installation success or error status: 1603. MSI (c) (30:60) [03:46:21:234]: Grabbed execution mutex. MSI (c) (30:60) [03:46:21:234]: Cleaning up uninstalled install packages, if any exist MSI (c) (30:60) [03:46:21:250]: MainEngineThread is returning 1603
  15. Latest Version of Software Running on XP

    Try the offline installer at https://java.com/en/download/manual.jsp UPDATE: Tried that and it's not working. After some quick debugging it seems that there is an access violation exception related to C runtime implementation. ANTIDEBUGGING related stuff. The resource section includes an MSI file, which cannot install for some reason. Using Orca tto see more info.