|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
122.174.162.255
In Reply to: RE: Configuring with nLite posted by play-mate on May 03, 2012 at 02:59:20
All of the above plus "Multi-Processor Support". Make sure to retain it as well. Its very simple to remove unwanted dll & sys files by editing the 'textsetup.oem' file that goes with your nLite install. By doing this, you would no longer need to opt for file deletions, as you would already omit them before install, by means of the textsetup.oem file. Same goes for adding drivers as well as executables like Cicsmemoryplayer.exe or Cicsplay.exe. Edit the file with Notepad & remove unnecessary files that u do not need...
Junaid
Follow Ups:
You will not be able to access GROUP POLICY EDITOR in MMC but it does not seem to matter.
Once you get to cPLAY and check AWE, DIAGNOSTICS will say AWE SUCCESSFUL - so who knows when and if AWE is ever really successful! It was written that if you asked for AWE and it was "not there" cPLAY would exit. Who knows ...
None of the rest is needed unless you just want it.
The system will work fine.
One nice thing about an nLite XP Pro install is that you can usually delete all of the unnecessary stuff at one time.
Hey Jolida,
Iīll be okay with the mulithreading in BIOS, but what do you mean by "textsetup.oem" ???
Cannot find this file; nor "txtsetup.oem".....
Can you explain further, please.
Do we (ayone) have a complete summary list of unwanted DLL and drivers (in this context)?
Canīt wait to get it all up and running....
kind regards
cMP2 Computer w/digital crossovers & FIR filters > Lynx Aurora 8 FireWire /192kHz all channels. 2x AcousticReality Ref. 202 & 2x AcousticReality Ref. 601īs ICEpower. Magnepan MG3.3R beechwood frames & custom stands. Miller chokes
When u create an NLite disc, opt to create the installation in a folder on the desktop instead of burning the image immediately to a cd. The folder will contain a sub-folder named i386. It's inside this folder that the file txtsetup resides. It may be named as txtsetup.oem or txtsetup.sif.
When windows starts installing, it creates a list of files to be copied for installation. It is from this txtsetup file that it gets info of what to install & what not to. You can edit this file using notepad & remove or add any file you wish to. At first, it may seem a bit confusing. Just open the file with Notepad & look at its contents. You will, in no time, understand how the data in it is written to instruct windows to install which file in what directory. You can customise your xp install just by editing this one file. But before that, u need to be certain as to what set of files actually need to remain for your cMp installation to work without throwing up a missing file error. Just a bit of homework & you are good to go.. After editing the file, u can then burn the image to a cd to start installation as usual...
Serge & Jack have done an outstanding job of taking cMp to a level which might have seemed impossible for even a software techie to accomplish. Great job ;)
Junaid
.
cMP2 Computer w/digital crossovers & FIR filters > Lynx Aurora 8 FireWire /192kHz all channels. 2x AcousticReality Ref. 202 & 2x AcousticReality Ref. 601īs ICEpower. Magnepan MG3.3R beechwood frames & custom stands. Miller chokes
Hi Leif,
I think Jolida is referring to the file LastSession.ini (or .inf) where you can find details on the installation and edit it through Notepad.
I highly recommend you not to restrict your cMP optimization to a classic one (by cics notes), otherwise SQ will be compromised - bass is missing. It seems that one has to go all the way with slimming optimizations to enjoy a full sound again.
You can keep your "normal cMP2" and compare it to "super cMP2" all the time...and then report back. :-)
It would be interesting to know from Steppe and other users who have implemented the change at what stage "sound is back", to know exactly what it made the "final" change for the better. Registry slimming?!
Hello, everybody!
First of all, I'd like to note, that Junaid's warning about multiprocessor support is extremely important, as it assures CORRECT hal.dll and correct initial kernel will be renamed to real hal.dll and ntoskrnl.exe DURING INSTALL. Yes, this is the windows' trick!
Next! It's much easier NOW to tell what files SHOULD remain after ALL, because the files to be deleted are LEGION.
I think that the difference between Julia and Lynx and Firewire-usb options will be 3-4 files, while their total number is less than a hundred.
I can once again post the pic of my system32 and drivers and fonts folder, or, if anyone needs, can write me for details. Warning! this is an NTFS-XP-PRO-LYNX version.
Serge.
Junaid! Welcome back!
Post a Followup:
FAQ |
Post a Message! |
Forgot Password? |
|
||||||||||||||
|
This post is made possible by the generous support of people like you and our sponsors: