|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
198.54.202.195
In Reply to: Re: 6. [New] Bypass Windows Explorer (User Interface) posted by texastea006@yahoo.com on April 20, 2007 at 15:24:35:
Very interesting – more air & blacker backgrounds!My Audigy 2 ZS Platinum (with kX driver) yields more improvements than my RME HDSP 9652. RME still edges out Audigy by a small margin. RME card has very latest software (firmware and driver @ version 3.02 March 2007). This RME software update gives better playback results (latency via ASIO/RME down to 0.32ms vs kX @ 0.25ms using Kernal Streaming/Audigy).
I’m posting 2 solutions (reply post to this) on how to automate this. Summary:
1. Can’t terminate all services as you get no playback from Foobar. Some Windows services are critical
2. Option 2 offers more aggressive culling of Windows
3. Must shutdown computer by pressing power button 4-5 seconds – force shutdown
4. Both options attempt to recover Windows UI after exiting Foobar – depending on soundcard, option 2 may not give Windows UI
5. Preference is to select option that gives Windows UI after exiting Foobar – in my case, only option 1 works for both cards
6. Not much sound difference between options even with option 2 being more aggressive
7. Don’t run .bat file at startup – rather double-click from Desktop until right option is chosen
8. Any changes made on desktop is not saved after exiting Foobar (as proper Shutdown doesn’t happen). On startup and before running .bat file, do necessary changes and reboot to save Desktop UI changes
9. Both options start Windows Task Manager (at lower priority). Very useful to see Windows processes being eliminated & memory freed. For information only – exit Task Manager at any time.
Follow Ups:
Another process utility (pskill.exe) is needed to kill process and its dependencies. Instructions copied into .bat file has ‘[YOUR SOUNDCARD PROCESS]’ – put your soundcard’s process here (e.g. kX = kxmixer.exe and RME = hdsp32.exe). Also remove ‘rem ’ prefix. Next instruction kills RME’s mixer process (if ‘rem ’ prefix removed).1. Download PSTools.zip from link below
2. Open zip file and copy pskill.exe (183KB) to c:\ (root directory)
3. Run pskill.exe (double-click on it) to do away with license agreement confirmation
4. Edit .bat file and clear all contents
5. Copy following instructions into .bat file
@echo off
rem # Kill Windows UI
start /wait c:\process.exe -k explorer.exerem # Start Task Manager
start C:\WINDOWS\system32\taskmgr.exerem # Kill Windows & VTTimer.exe (for Biostar mobo using VIA chipset)
start /wait c:\process.exe -k VTTimer.exe
start /wait c:\process.exe -k smss.exe
start /wait c:\process.exe -k winlogon.exe
start /wait c:\pskill.exe -t lsass.exe
start /wait c:\pskill.exe -t svchost.exerem # Adjust priorities, eg. High, RealTime, BelowNormal, Low
start /wait c:\process.exe -p taskmgr.exe Normal
rem start /wait c:\process.exe -p [YOUR SOUNDCARD PROCESS] AboveNormal
rem start /wait c:\process.exe -k hdspmix.exerem # Start Foobar
start /wait /REALTIME c:\progra~1\foobar2000\foobar2000.exerem # Start UI after Foobar
start /wait /B c:\windows\explorer.exe6. Test by double-clicking .bat file
I wanted more of Windows culled without loosing Windows Explorer UI (after exiting Foobar) and came up with this solution. Explorer is suspended (that way all its inference stops) and resumed after Foobar is exited. This will work with all soundcard drivers. By suspending Explorer, no CPU resources are consumed but unfortunately, memory remains allocated to Explorer.I get best results using this option.
Please don’t minimize Foobar – you MUST exit to get back to Explorer. Once application is minimized, it cannot be restored (as explorer is suspended).
Under step 5 (of option 2), use these instructions:
@echo off
rem # Suspend Windows UI
start /b /wait c:\process.exe -s explorer.exerem # Start Task Manager
start /b C:\WINDOWS\system32\taskmgr.exerem # Kill Windows & VTTimer.exe (for Biostar mobo using VIA chipset)
start /b /wait c:\process.exe -k VTTimer.exe
start /b /wait c:\process.exe -k smss.exe
start /b /wait c:\process.exe -k winlogon.exe
start /b /wait c:\pskill.exe -t lsass.exe
start /b /wait c:\pskill.exe -t svchost.exerem # Adjust priorities, eg. High, RealTime, BelowNormal, Low
start /b /wait c:\process.exe -p taskmgr.exe Normal
rem start /b /wait c:\process.exe -p [YOUR SOUNDCARD PROCESS] AboveNormal
rem start /b /wait c:\process.exe -k hdspmix.exerem # Start Foobar
start /wait /REALTIME c:\progra~1\foobar2000\foobar2000.exerem # Resume Windows UI
start /b /wait c:\process.exe -r explorer.exe
This solution revises 'Signature Edition' and has no side effects! This means you can do a normal shutdown after Foobar or whatever else.Explorer is killed and started (before and after Foobar). Windows stuff is suspended & resumed. This will work with all soundcard drivers. By killing Explorer, memory is freed. Further improvement in sound is gained.
Other changes include:
1. Under rem #1 (remark #1) provision for Process Explorer - default starts Task Manager but if you prefer Process Explorer then copy procexp.exe file to c:\ and remove 'rem ' prefix from procexp.exe line. Also add 'rem ' prefix to rem #1 & #4 taskmgr.exe lines.
2. Don't need to use pskill.exe utility
3. Under rem #4, as before, you can change your soundcard driver setup utility priority. For RME, the mixer can also be killed. For Biostar mobo, VTTimer.exe can be killed. These are done by removing 'rem ' prefix in appropriate line
Under step 5 (of option 2), use these instructions:
@echo off
rem #1 Start Task Manager
start /b C:\WINDOWS\system32\taskmgr.exe
rem start /b c:\procexp.exe /p:nrem #2 Kill UI
start /b /wait c:\process.exe -k explorer.exerem #3 Suspend Windows
start /b /wait c:\process.exe -s smss.exe
start /b /wait c:\process.exe -s winlogon.exerem #4 Adjust priorities, eg. High, RealTime, BelowNormal, Low;
rem # and do housekeeping (other cleanups)
start /b /wait c:\process.exe -p taskmgr.exe Normal
rem start /b /wait c:\process.exe -p [YOUR SOUNDCARD PROCESS] AboveNormal
rem start /b /wait c:\process.exe -k hdspmix.exe
rem start /b /wait c:\process.exe -k VTTimer.exerem #5 Start Foobar2000
start /wait /REALTIME c:\progra~1\foobar2000\foobar2000.exerem #6 Resume Windows & Start UI
start /b /wait c:\process.exe -r winlogon.exe
start /b /wait c:\process.exe -r smss.exe
start /b c:\windows\explorer.exe
Noticed good sound improvements with this!In addition, I'm still experimenting with changing affinity. I can definitely hear a difference, but can't decide which sounds more accurate.
Ed,
See my latest reply to this post and try my setitings:
http://www.audioasylum.com/forums/pcaudio/messages/20187.html
don't forget to run process explorer by system internals (free) or some other program so you can change the settings for the cmd.exe which starts once the batch file has been executed.
Let me know if the changes are positive.
Only need Process Utility (process.exe) as per change item 6. Instructions copied into .bat file has ‘[YOUR SOUNDCARD PROCESS]’ – put your soundcard’s process here (e.g. kX = kxmixer.exe and RME = hdsp32.exe). Also remove ‘rem ’ prefix. Next instruction kills RME’s mixer process (if ‘rem ’ prefix removed).1. Edit .bat file and clear all contents
2. Copy following instructions into .bat file
@echo off
rem # Kill Windows UI
start /wait c:\process.exe -k explorer.exerem # Start Task Manager
start C:\WINDOWS\system32\taskmgr.exerem # Kill Windows & VTTimer.exe (for Biostar mobo using VIA chipset)
start /wait c:\process.exe -k VTTimer.exe
start /wait c:\process.exe -k smss.exe
start /wait c:\process.exe -k winlogon.exerem # Adjust priorities, eg. High, RealTime, BelowNormal, Low
start /wait c:\process.exe -p taskmgr.exe Normal
rem start /wait c:\process.exe -p [YOUR SOUNDCARD PROCESS] AboveNormal
rem start /wait c:\process.exe -k hdspmix.exerem # Start Foobar
start /wait /REALTIME c:\progra~1\foobar2000\foobar2000.exerem # Start UI after Foobar
start /wait /B c:\windows\explorer.exe
First, I need to ask (unrelated again).. my computer only has usb connections for mouse and keyboard (no serial), so I have not turned off usb connections in the bios. Will that disable my usb connections permenantly? Can I still use my usb input devices in the bios? in windows? if I disable it in the bios?
Lastly, I have not had a chance to try these options, although I have no doubt that the improvements will be significant. I can remember when I killed all those processes how good it sounded, and I will create the batch files as soon as I am ready to let the pc sit for a long time without needing to reboot.
I don't have any more ideas, so as far as I'm concerned, this is just about the final frontier as far as tweaking windows goes. I will include all of these changes when I have a dedicated media pc, and will keep an eye out here for any other additions.
Are you updating your pdf file with all of these additions and is that available for download?
USB BIOS: Yes it would disable USB connections (haven't tested though). So don't disable USB in BIOS. I also use USB wireless mouse. I have EHCI disabled but USB Controller is enabled.QP Noise Disruptor & Shakti Stones: Never tested stones. On QP Disruptor, after installing Zalman TNN-300 case, I found it congested the sound. After each improvement, I retest and so far, its best without the Disruptor. I would definitely try to remove PCIe graphics card. An option would be to output XGA/SXGA via mobo video to DVDO's VP30 or VP50 - its an external video processor with brilliant picture quality.
Change 6 (Bypass Windows Explorer): I found a way to prevent force shutdown of Windows. I'll post a revision to Option 2's (Signature Edition). It works very well and you can run it during Startup. After exiting Foobar, Windows and Explorer is fully available. This .bat file can be started as many times and there should be no Windows problems.
Update PDF version 0.1: I've posted a change on Foobar forum for .cue file playback bug where no full file buffering occurs. So I'm going to wait for next Foobar release before I release version 0.2. They have released 0.9.4.3 which still has the bug.
| ||||||||||||
|
This post is made possible by the generous support of people like you and our sponsors: