|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
128.70.41.115
In Reply to: RE: The complete NEPTUNE KERNEL WALKTHROUGH posted by steppe on April 23, 2012 at 07:03:35
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.
Follow Ups:
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.
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: