|
Audio Asylum Thread Printer Get a view of an entire thread on one page |
For Sale Ads |
82.156.128.160
In Reply to: RE: The Big Substitutions TWEAK posted by steppe on January 19, 2012 at 21:09:42
Hi Serge,
Is there a way too check which kernel is actually loaded at startup?
(Situation A)
It is my impression that if one retains the ntkrnlpa, the boot.ini string “/KERNEL= yournamekernel.exe “ is ignored and the ntkrnlpa.exe is still loaded (despite the boot.ini string).
(Situation B)
If I rename the exe-file extensions from botch ntkernelpa.exe and ntoskernel.exe too *.bac and put the ntoskernel.exe (w2k-version) in place, I get an error message at startup there are DLL’s missing.
If in situation A the ntoskernel.exe from w2k was loaded through use of the boot.ini string, than I should have gotten that same error.
But I didn’t got that error.
So an alternative kernel is loaded in situation A.
Probably the ntkrnlpa.exe because it is retained.
Mark
cMP2 PC > ESI Juli@ > Van den Hul Optocoupler MkII > Lavry Black DA10 > XLR Mogami Gold > Klein & Hummel O300
Follow Ups:
to load yourname with ntoskrnl.exe present or with ntkrnlpa present. In both cases you need at least one native kernel to be present. Nt loader checks to see that you have at least one. To, say load w2k kernel with ntkrnlpa and to be sure it is w2k kernel, that is at work, specify /KERNEL=yourname.exe in the beginning of the string AND /nopae closer to the end - this comand FORCES nt to start with either ntoskrnl.exe or with alternative one. If you retain ntoskernl.exe and delete ntkrnlpa, then use /kernel=yourname.exe, but at any time ONE NATIVE should be present, thus any time with alternative kernel there are TWO kernel a native one and alt. one, But to use and load in memory ONLY ONE kernel, use your native ntoskernel.exe from xp. This way, though it's bigger you assure the best memory-cpu interaction and absence of the secondary kernel in memory. It seems to me it sounds more robust, vivid but without harshness, while with w2k and ntoskernel(native) together the sound is smmother but slightly dull.
Serge.
P.S. Hope it's not confusing.
I tried as you suggest: "If you retain ntoskernl.exe and delete ntkrnlpa, then use /kernel=yourname.exe" taking it to mean I rename ntoskrnl.exe, say to ntriboge.exe, then remove ntkrnlpa and in boot.ini up front put /KERNEL=ntriboge.exe. Is this correct?, because it didn't work causing cycling of startup just like simply removing ntkrnlpa. My computer may somehow be different because I was also able to substitute win2k ntoskrnl without /kernel and renaming.
I also tried leaving in /KERNEL=ntriboge.exe while not renaming ntoskrnl.exe just to see (since your instruction is a little ambiguous) but no surprise that did no better.
Any suggestions?
rename xp native ntoskernl. It should remein unchanged. Once you do it You get a black screen on reboot and you will have to remove the file and paste it back, also remove all logs that were created by registry hive.
in othe words you have 4 kernel options
1, two native kernels
2. one native kernel. but only ntoskrnl.exe and /nopae switch
3. w2k + ntkrnlpa + /nopae switch
4. w2k + ntoskrnl
Leave at least one native kernel unchanged
5. option to use only native ntkrnlpa can be possible but you need 4 gb physical ram, /PAE and /3GB switches.
Hope, this is it.
Serge.
When I try to do your 2., as I said, I do not get a black screen but a restart before anything shows up over and over until hard shutdown. This is with renamed ntoskrnl.exe and no ntkrnlpa and with /nopae. Nonetheless I will go on to cut and then past ntoskrnl.exe and remove all hive logs and see what happens.
That it should be THE NATIVE kernel. Don't give its name to alternative one. ntoskrnl.exe should ALWAYS be the real native one.
Serge.
As for e-mail, some things were made there that make a lot of cics' optimisations done or unnecessary, but the services were untouched, and some othet things, so You better treat it as a minixp. It should install easily and without oobe, serial, regs and so on. Video was already set, most things removed. When installing weiss or other things, be patient, please, it takes looonger. Awe and minlogon should work like a charm as they were described. WFP was already removed. There is also a session.ini file that you may see what was done, if you have nlite, just load the ini files from the iso. It's very easy to navigate.
Serge.
Without ntkrnlpa I have, of course, only been trying with the native ntoskrnl. I tried it after cut and paste and removal of hive logs both as "ntoskrnl.exe" and as "ntriboge.exe" with /KERNEL=ntriboge.exe but neither got anything but recycling restart as before.
The nlite xp allowed Weiss install normally as well as Intel ethernet install and that for cMP/cPlay, but it did not recognize the net command in command window despite network running.
I thought you had stated previously that ntkrnlpa was insufficient by itself. If that is so "to be sure it is w2k kernel, that is at work, specify /KERNEL=yourname.exe in the beginning of the string" would seem unnecessary if one has removed native xp ntoskrnl and is using win2k one with ntkrnlpa.
If that is not the case, then why not use just ntkrnlpa on purpose?
hfavandepas, there IS a reason: you might prefer the sq even though steppe doesn't. I like it that way but have not so far gotten a successful try at using the original kernel alone to see whether or not I find it better myself.
nt
cMP2 PC > ESI Juli@ > Van den Hul Optocoupler MkII > Lavry Black DA10 > XLR Mogami Gold > Klein & Hummel O300
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: