|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
128.70.22.24
In Reply to: RE: cPlay - the open source high-end audio player using ASIO posted by cics on May 05, 2008 at 12:31:58
Hello, everybody!
First of all, I must apologize for sending INCORRECT INSTRUCTIONS before with neptune pack, concerning the neptune.exe introduction.
This is the right thing now, with all due switches, a-la MS, booting, rebooting, rebooting to tighter memory timings, everything works, even after unplugging the powercord from the wall outlet.
0. Make sure that Your cmp works, as usual, wo a problem.
1. Copy the neptune.exe file to Your system32 folder.
2. Open Your boot.ini with the notepad and enter this switch AFTER
/fastdetect
/KERNEL=neptune.exe
(please, note, that original file was neptune.exe, not Neptune.exe or NEPTUNE.EXE)The following is my WORKING boot.ini string:
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=alwaysoff /fastdetect /KERNEL=neptune.exe /maxmem=512 /UsePMTimer /timeres=2441 /nodebug /pcilock /nopae /onecpu /noguiboot /MININT
Please, note, that there are NO double spaces and ANY ADDITIONAL spaces between or before the switches.
Make sure that notepad is not set to auto break strings or auto word wrap or any other comand in Format menu.
3. Copy ntkrnlpa.exe file from Your iso and don't forget to decompress it to system32 folder.
4. Rename Your existing ntoskrnl.exe to ntoskrnl.old (never mind the warnings)
5. Reboot. If You have made everything carefully and correctly, You will hear this magic immediately, not after 3-4 days, as I wrote before (explanations later)
6. Now, You will probably LOVE what You hear, but if You reboot now, You will get a nasty ntoskrnl.exe failed notice. WHY SO. That was the thing I faced with w2k kernel, and we have experienced with Grant and Rick. The problem is, that the /kernel= switch is for debugging of experimental kernels and this feature seems to be a one-time only. On reboot, our kernel itself MODIFIES ntldr and ntdetect, preventing You to boot it again, unless, ... You change the SYSTEM DATE IN BIOS. Every wise man has a lot of simplicity in him, as we say in our country. So, to make the change permanent (is 12 years enough for You?)
7. Close cmp, and when it asks, if it should reboot after the system shutdown, say yes, the system will start rebooting, so immediately ENTER the BIOS SETUP and change the system date to the earliest possible. Mine is now at 01.01.2000. press F10 to save changes to bios and let the system reboot. You ARE THERE!!!
Enjoy.
Serge.
P.S. I wish to express my gratitude to Rick and Grant for being as obsessive with finding the truth as myself and for expressing healthy doubts to focus my attention to the problem.
Edits: 04/23/12Follow Ups:
Hello, everybody. I must confess, my instructions were wrong AND the neptune.exe files themselves BOTH TIMES were WRONG.
I was making dozens of reboots and substitutions and simply got lost in all these boot.ini-s and file versions.
That time I had written about everything playing well, my neptune kernel was called neptunee.exe (smallest difference) to confirm to 8.3 standard in an attempt to somehow fool the ntldr-ntdetect.com. While in the boot.ini I had /KERNEL=neptune.exe. So in fact the kernel wasn't working at all and all my time-date tweak is false, for it doesn't work.
Now, the file that really works, is here, it's really a NT 3.1 kernel, not NT 3.5.1, - another thing that worked to mislead myself.
Well, only about two hours ago I found this thing. I am sorry. The file would boot only once, certainly, though You can easily boot it any time, Simply, it requires a certain procedure.
First, the neptune.exe should be in system32
Edit Your boot.ini, just like MS says we should (after fastdetect) /KERNEL=neptune.exe
It boots wo a problem, plays very well, it's much more resolving and smooth.
When You need to power down, just power down, but to boot with normal kernel next time (and You can only boot with a normal kernel next time), You need to do the following exactly and only in the followind sequence:
1. Edit boot.ini to DELETE the /KERNEL=neptune.exe switch
2. Delete win.ini file
3. Overwrite Your ntldr and ntdetect.com with a fresh pair from Your iso or, like me, from a reserve folder.
Reboot.
If You do this correctly, You won't get the ntoskrnl.exe error.
This way the whole procedure of using neptune, powering down and rebooting with normal kernel takes appr. 5 minutes.
I know that it's a PITA, but this way we can use it, at least, for some more important and longer sessions.
Serge.
Anyone who is STILL INTERESTED, can e-mail me to get the right one.
Hi Serge just a question or 2:
1) put the new neptune in system32 (leave both ntoskrnl and ntkrnlpa in sys32?)
2) amend boot.ini with kernel = neptune.exe
3) boot & enjoy great music
4) When you have to shut down amend boot.ini, delete win.ini, overwrite ntldr and ntdetect and boot into normal kernel
5) Go back to 1 to get the good kernel
Do I have it right?
Hello, again, Ted! You do not need TWO original kernels. Keep just the one You were usually listening to say, ntoskrnl.exe or ntkrnlpa.exe
Everything else is right. Just be sure to observe the sequence of deletions to reboot to "normal" non-neptuned state wo an error.
Serge.
I usually power up once a day, so for me the whole procedure is not a problem, exept it doesn't allow me to reboot to enter the cmp-extreme memory timings, but it's another story.
One more question for you Serge (and btw I'm nutty enough to live with this if I can get it to work and do I appreciate your efforts in making cmp a great sounding pc system) but what if I Snapshot my neptune kernel system and my regular kernel system and save those SS files. Then on an ongoing basis why could I not just restore my CMP disc with one or the other prior to rebooting? In fact why not restore the initial OS with neptune everytime I reboot? What tells the pc that the boot into it is the 1st or 2nd boot? With Jwindows so small I can Snapshot it back up in under 7-10 seconds. This I can definitely live with if I can get it to work.
I think, exept, You will be fragmenting Your drive very quickly.
Serge.
But I am not sure now. What if ntldr and ntdetect.com won't snapshot well? They are VERY TRICKY.
On the run up to where I am right now I have SS my ssd probably 200 times since last year. Always worked well. Think I'll try.
I feel I am not getting the whole picture here...
Where is this kernel file?
Have you been experimenting with other users?
What Iso?
Is it safe to change for ANY cMP user?
is availible in different places. E-mail me for details now.
Serge.
Folks! This tweak isn't yet tested with Your Home windows, so, I suggest that You
do not use ntkrnlpa.exe.
Instead, leave Your ntoskrnl.exe intact,
DO NOT rename it and
do not introduce ntkrnlpa.exe to Your system32.
Everything else remains the same.
Serge.
Be attentive! If Your neptune file is Neptune.exe, the syntax in boot.ini should be /KERNEL=Neptune.exe
If Your neptune file is Neptune.exe . . .
It's probably an age thing but I'm getting confused here. If "Neptune.exe" is the NT 3.5 kernel (BTW and IMHO, NT 3.5 was possibly Microsoft's best ever OS), why are we using boot.ini's Kernel switch? Why not just rename Neptune.exe to ntoskrnl.exe and replace the XP version?
I ask because, when I tried the Kernel switch on my Intel D510 cMP system, everything seemed OK though it wouldn't work on my Fit-PC2 setup. Fiddling with this and that to get to grips with the issue, I renamed Neptune.exe and deleted the switch on the Intel board: the system booted and allowed VNC access over the LAN but would not logon to the music "server".
I'm wondering therefore if the replacement kernel was in fact not loaded when invoked by the boot-dot-ini switch but was when the XP file was replaced. In short, how can one be sure which version one is running - if at all?
I have tried renaming the neptune file to ntoskrnl.exe with ntkrnlpa.exe present in the system. The system will boot... ONCE. It was then that my suspicions became certainity - the ntldr doesn't only have a hardcoded feature to recognize the name ntoskrnl, but each version of nt, xp or w2k has its own ntldr + ntdetect.com that work only with their native kernels. others will boot once for debugging session. I have compared sizes, and the ntldr and ntdetect.com sizes are different for all versions. I have tried using nt3.5 ntldr in xp, The system won't even start, which is easily explained, because not only kernel, but also, HAL.dll is involved in the boot process, and while kernel is the same for all versions (the size is different because of unnecessary crap), the hals are different. So, the only supposition was that the date-time stamp on ntldr and ntdetect.com are the culprit. Also, any ntfs.sys or ntoskrnl error is "spoiling" the nice pair - ntldr and ntdetect.com. We greately underestimate/neglect the role of these two. In fact, any burnt down Windows system can be easily repaired with a little manual editing of the registry and overwriting ntldr-ntdetect.com pair with a fresh copy from the iso. So it goes.
You can say that the new kernel WAS working, if the system doesn't boot immediately after the experimental session, if the sound quality change is not enough.
Serge.
Certainly, I haven't tried the thing in Your setup configuration...
Edits: 04/23/12 04/23/12
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: