.jpg.4f7bba1bf6916974696da592ded201ad.jpg){kind=avatar}
robertcollier4
Content Type
Profiles
Forums
Events
Posts posted by robertcollier4
-
-
Better to go to VideoHelp for downloads of PotPlayer. The latest version for Windows XP is marked there and it is 1.7.17508 which works flawlessly with WinXP including X265:
https://www.videohelp.com/software/PotPlayer
Find: Download PotPlayer 1.7.17508 for Windows XP Adfree
Find Download PotPlayer 1.7.17508 for Windows XP 64-bit AdfreeDo not use versions after this because it breaks X265 compatability because of "1.7.20538 Changed default HEVC decoder to Built-in FFmpeg HEVC H/W Decoder". Windows XP cant do HEVC H/W decoder.
0 -
https://tweakhound.com/2015/12/05/windows-10-services/
http://www.askvg.com/beginners-guide-to-configure-windows-10-services/
http://www.ghacks.net/2015/11/28/windows-10-new-services-list/
http://www.askvg.com/master-tutorial-to-make-windows-10-super-fast/
https://www.wilderssecurity.com/threads/windows-10-which-services-disable.378804/0 -
http://www.hydrogenaudio.org/forums/index.php?showtopic=102875
Conclusions & Observations:
The Apple AAC had the best quality among the 4 encoders tested. The Apple AAC was clearly superior than the Microsoft WMA. LAME MP3 was worse than the WMA, and VisualOn vo-aacenc was the worst encoder.http://wiki.hydrogenaudio.org/index.php?title=Hydrogenaudio_Listening_Tests
0 -
http://www.youtube.com/watch?v=ay-gqx18UTM
http://www.youtube.com/watch?v=ToFgYylqP_U
This video demonstrates the slowness of the new Windows 7 GUI.
Windows Display Drivers Model used in both Vista and 7 doesn't include the neccesary hardware accelerated 2D functions to make the graphics generated by GDI and GDI+ as fast as in Windows XP.
Microsoft chose software render because they found too difficult to combine the new graphical engine with the old one. If you want to learn more about it read this: http://blogs.msdn.com/directx/archive/2009/05/12/2d-drawing-apis-in-windows.aspx
GDI has dozens of functions: http://msdn.microsoft.com/en-us/library/dd145203(VS.85).aspx
GDI hardware acceleration in Windows 7 using WDDM 1.1 drivers has only these functions hardware accelerated: http://msdn.microsoft.com/en-us/library/dd434692.aspx
WDDM 1.1 drivers makes mandatory this new "partial" GDI hardware acceleration. So any driver which claims to be 1.1 is already accelerating as much as it ever will.
Too bad, the results I got were based on WDDM 1.1 drivers (both from nvidia and Microsoft itself).
http://www.passmark.com/support/performancetest/2d_windows7_performance.htm
2D results in Windows 7 seem poor compared to previous versions of Windows, why is this?
Different Windows applications use different methods of drawing to the screen. Some applications render directly to the window, which is the same method used in the vector tests in PerformanceTest (GDI+ to a hWnd). These application will likely suffer a performance hit in Win7. Other applications render to a buffer in main memory and then use a method known as bitblt to push the final image to the screen buffer (GDI+ to a DIB section then bitblt). This method is known as double buffering. Most large commercial applications (such as Word and Photoshop) use this later method and will not suffer much if any performance degradation in Win7. There is a discussion of this on Microsoft's graphics performance blog.
http://www.neowin.net/forum/topic/1036369-did-you-know-all-gdi-apps-render-slower-under-win7/
DWM redirects window draw routines to an offscreen buffer and then re-draw them back to the main screen. That means for any window, DWM is redrawing their contents... twice. Coupled this with slower GDI performance than Windows XP. On the other hand, DWM will ensure the contents of the window fit in before it redraws the whole window, so when you drag the window around, it won't cause graphical glitches because now the window will only be redrawn when it's complete.
On the other hand, not using DWM will free up a lot of CPU resources. But still not enough to make GDI render operations as fast and responsive as Windows XP, as XP has more CPU free to do other tasks. If there is a fix for this, I would love to know, too... but it seems like this is already an integral part of Windows 7. The driver model has had to be rewritten to accomodate the new driver device interface (DDI) of DirectX 10 and beyond, and they had to shaft GDI hardware acceleration to accomplish that. They chose to remove GDI hardware acceleration as they found it hard to combine both driver model features. So there is no likely fix in the future except for a whole new edition of Windows.
0 -
Here is a potential thing to add to nLite for Windows XP. "Fix svchost.exe 'memory could not be read' error on shutdown".
There is a common error related to svchost.exe that occurs on stripped versions of Windows XP in which services have been tweaked/disabled. The error on shutdown (only appears sometimes) is:
svchost.exe - Application ErrorThe instruction at "0x7c92dd29" referenced memory at "0x00000008". The memory could not be "read".ORsvchost.exe - Application ErrorThe instruction at "0x7c92c288" referenced memory at "0x00000008". The memory could not be "read".
The problem is that Windows has used an update pack that included a non-official "QFE" branch of KB971657 which updates wkssvc.dll to a buggy QFE edition. The fix is to downgrade wkssvc.dll back to the stable GDR version.Attention! Updating information.
Issued 11.08.2009 Security Update KB971657, when installed on the QFE branch, causes an error when you restart the svchost.exe. GDR branch of the hotfix, the test results are not affected by the problem. For those who are in the tank - hot fixes for XP, as a rule, contain two versions of one and the same file.
If you have after installing KB971657 discussed error occurred, check the full version of the file wkssvc.dll in System32, as described in this post, and if it turns 5.1 .2600.5826 (xpsp_sp3_ qfe .090609-1445), replacements , and those files GDR option
The fix first found found by os-zone here1 and here2 and full thread and ru-board here but translated and simplified by Sergey Kireev here. Just need to extract WindowsXP-KB971657-x86-ENU.exe with the "/x" switch and then replace wkssvc.dll with the file from the SP3 GDR branch:
_http://social.msdn.microsoft.com/Forums/en-US/d427ca47-869c-4c6b-b151-7ad60482c68d/svchost-error-at-shutdown1. Download the KB971657 hotfix:_http://www.microsoft.com/downloads/details.aspx?familyid=9c0e5bff-c248-4e87-a83b-82ba52f5299d&displaylang=en2. Extract the content of the WindowsXP-KB971657-x86-ENU.exe to the temp folder:WindowsXP-KB971657-x86-ENU.exe /xThis hotfix includes 4 versions of the same file http://support.microsoft.com/default.aspx/kb/971657For all supported x86-based versions of Windows XPFile version File size Date Time Platform SP requirement Service branch Wkssvc.dll 5.1.2600.3584 132,096 10-Jun-2009 06:32 x86 SP2 SP2GDR Wkssvc.dll 5.1.2600.3584 134,144 10-Jun-2009 06:26 x86 SP2 SP2QFE Wkssvc.dll 5.1.2600.5826 132,096 10-Jun-2009 06:14 x86 SP3 SP3GDR Wkssvc.dll 5.1.2600.5826 134,144 10-Jun-2009 06:17 x86 SP3 SP3QFE 3. Replace your buggy QFE edition of C:\windows\system32\wkssvc.dll with the stable file from GDR subfolderFor example:C:\WindowsXP-KB971657-x86-ENU\SP3GDR\wkssvc.dll for SP3 image
NOTE: You can check which version of the file you have as shown in the following images. The QFE version is buggy. The GDR version is good.0 -
I am getting the below "The system cannot find the file specified" error when trying to remove packages with install_wim_tweak. I am trying to remove packages using a WinXP SP3 x86 host system.
set MNT="E:\Mnt\Win7ProNSP1"
install_wim_tweak.exe /p %MNT% /r /c Microsoft-Windows-BLB-Client-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514-------------------------------------------
--------Registry Tweak Tool v1.4.6.0-------
---------------for Windows 6.x-------------
---------Created by Michal Wnuowski--------
-----------Modified by Legolash2o----------
-------------------------------------------
MountPath : "E:\Mnt\Win7ProNSP1"
Component : "Microsoft-Windows-BLB-Client-Package"
------------------Starting-----------------
Creating BKP of registry file... OK
Mounting registry file... OK
Taking Ownership... OK
Editing 'Packages' subkeys 1/1OK
Editing 'PackagesPending' subkeys 1/1OK
Modifying registry completed sucessfully.
Unmounting key... OK
Removing 'Packages'... 1/1The system cannot find the file specified
OK
Removed packages successfully.
Removing 'PackagesPending'... 1/1The system cannot find the file specified
OK
Removed packages successfully.
-------------------Ending------------------Update: Figured it out if I use dism.exe instead it works fine. I used install_wim_tweak to unhide all the packages.
install_wim_tweak /p %MNT%
dism /image:%MNT% /Remove-Package /PackageName:Microsoft-Windows-Backup-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514The way I recommend is that to:
0. Set your vars
set MNT="E:\Mnt\Win7ProNSP1"
1. Use install_wim_tweak to unhide all the packages
install_wim_tweak /p %MNT%
2. Use DISM to get a list of all packages and export it to a text file:
dism /image:%MNT% /Get-Packages > Dism_Get_Packages_List.txt
3. Then use a text editor with good search/replace functionality and replace "Package Identity : " with "dism /image:%MNT% /Remove-Package /PackageName:" and remove all other metadata lines. Then go through that full package list and delete or REM out the lines for the packages you don't want to remove (using pdf from liquid0624 for reference to choose). Save that as a batch file and run.
0 -
I was working with a pre slipstreamed CD and I thought DPsXtrct.exe was the official DriverPacks install tool that everyone used but could find very little information on it. Turns out from submix8c's post, that it is just a one-off GUI written by a community member.
http://stanimirovi.com/Driver/usb_boot/usb_prep8/presetup.cmd
I found an official presetup.cmd example created by the official Driverpack tool and the way it does it is just with un7zip.exe. So I replaced the line calling DPsXtrct.exe in presetup.cmd with:
%CDDRIVE%\OEM\bin\un7zip.exe %CDDRIVE%\OEM\DP*.7z %SystemDrive%\
Thanks.
0 -
I am trying to make a completely unattended installation with no prompts and no options. It has DPsXtrct.exe launched from presetup.cmd as is normal for Driver Pack Extractor.
However - it gives the below extractor prompt - and if the user moves the mouse over the window - then the "Auto-Extraction" 1-minute countdown timer goes away. So it now becomes no longer unattended! If the person accidently moves the mouse - then they have to do something! I want to make it so that it always auto extracts with no delay and theres nothing the user can do to change it.
Does anyone know how to make DPsXtrct.exe auto-extract with no delay?
0 -
Well...anyways, I am stumped trying to find a good DOS or Win16 utility that will resize the partition without destroying the data on the hard drive.
PartitionGuru 4.x can resize a partition via its bootable FreeDOS utility bootdisk.
Downoad the full app here:
http://www.eassos.com/partitionguru/download.php
Download just the FreeDOS boot image here for use in a bootloader such as Grub4Dos:
http://sites.google.com/site/webuploads7373/PartitionGuru420FreeDOS.ima.gz
Grub4DOS menu.lst entry:
title PartitionGuru420FreeDOS.ima.gz [inmemory]
map --mem /iso/PartitionGuru420FreeDOS.ima.gz (fd0)
map --hook
root (fd0)
chainloader /kernel.sys0 -
Hashish GUI by SKAN (Autohotkey Script) This is also quite good if looking for a lightweight utility (not a Windows Property Page):
The .ahk file can be compiled into an .exe with the AutoHotKey compiler which allows you to do "HashishGUI.exe %1"
0 -
-
Thanks Fernando, using "32bit Intel RST AHCI & RAID driver v11.2.0.1006 mod by Fernando" - working great with Windows XP on a Thinkpad T61 with ICH8.
Also - for slipstreaming manually without nLite, I recommend this guide:
In my experience - I first tried it with just iastor.sys - and installation went through first phase - but then at reboot gave Blue screen. But then I included all the files in $oem$\$1\drivers - and it worked perfectly. So make sure to include all the files and set OemPnPDriversPath to the location of the files.
0
RyanVM might be shutting down
in Websites and Boards
Posted · Edited by robertcollier4
WinCert seems to be the next place for that kind of content that was at RyanVM. They have a files section that have many of the repacks integrators famous reuploaded from RyanVM (such as ricktendo and user_hidden). RyanVM was most famous for its repacks (switchless installers and lite installers) Recommend everyone post the files they have from RyanVM there on the WinCert files subsection that has file storage functionality.