MSFN Forum: problem with unattended boot screen kernel - MSFN Forum

Jump to content



  • 5 Pages +
  • 1
  • 2
  • 3
  • Last »
  • You cannot start a new topic
  • You cannot reply to this topic

problem with unattended boot screen kernel Rate Topic: -----

#1 User is offline   ihaveabu 

  • Junior
  • Pip
  • Group: Members
  • Posts: 94
  • Joined: 21-August 04

Posted 26 August 2004 - 06:46 PM

I'm having some problems making the boot screen show up. I used this guide:
http://board.msfn.or...?showtopic=9421
and the pinned guide by bor3d
but neither works. i've tried putting

Quote

bootcfg /RAW /A /Kernel=OEMKrnl.exe /ID 1
bootcfg /Timeout 0
bootlogo.cmd and this in winnt.sif:

Quote

[GuiRunOnce]
%systemdrive%\install\bootlogo.cmd
(with the cmd in the install folder next to start.cmd)
and i've tried

Quote

[GuiRunOnce]bootlogo.cmd

as said in the pinned guide, but neither works. a box pops up and says bootlogo.cmd can't be found.
am i doing something wrong?
i put the oemkrnl.exe in:
\XPCD\$OEM$\$$\System32\
i also tried:

Quote

[COMMANDS]"useraccounts.cmd"
"REGEDIT /S regtweaks.reg"
bootcfg /RAW /A /Kernel=OEMKrnl.exe /ID 1
bootcfg /Timeout 0

and saved as cmdlines.txt
as described in the guide by gosh.
i still boot with the same old boot screen as b4.
:} :no: :realmad: :wacko:

help?


#2 User is offline   ihaveabu 

  • Junior
  • Pip
  • Group: Members
  • Posts: 94
  • Joined: 21-August 04

Posted 26 August 2004 - 07:04 PM

help?

#3 User is offline   jrzycrim 

  • Friend of MSFN
  • PipPipPipPipPip
  • Group: Members
  • Posts: 769
  • Joined: 17-March 04

Posted 26 August 2004 - 07:17 PM

Remove the GuiRunOnce stuff.

Remove these lines from cmdlines.txt:
bootcfg /RAW /A /Kernel=OEMKrnl.exe /ID 1
bootcfg /Timeout 0


Place your bootlogo.cmd in $OEM$

Add this line to cmdlines.txt:
"bootlogo.cmd"


I'm assuming your bootlogo.cmd contains the lines I told you to remove from cmdlines.txt

#4 User is offline   ihaveabu 

  • Junior
  • Pip
  • Group: Members
  • Posts: 94
  • Joined: 21-August 04

Posted 26 August 2004 - 07:45 PM

jrzycrim, on Aug 26 2004, 07:17 PM, said:

Remove the GuiRunOnce stuff.

Remove these lines from cmdlines.txt:
bootcfg /RAW /A /Kernel=OEMKrnl.exe /ID 1
bootcfg /Timeout 0


Place your bootlogo.cmd in $OEM$

Add this line to cmdlines.txt:
"bootlogo.cmd"


I'm assuming your bootlogo.cmd contains the lines I told you to remove from cmdlines.txt

oh! quotes! i'm so dumb. i'll try it out. thanks.

#5 User is offline   ihaveabu 

  • Junior
  • Pip
  • Group: Members
  • Posts: 94
  • Joined: 21-August 04

Posted 26 August 2004 - 07:50 PM

one more thing:

Quote

Wallpaper:
To change your default wallpapers, simply place the image file which you wish to have as your wallpaper into into $OEM$\$$\Web\Wallpaper - If this directory does not exist, now would be a good time to create it

To actually set your default wallpaper to something different, orther than Microsoft's default grassy hills wallpaper (bliss.bmp), you need to use a little regristry tweak.

Add this to your tweaks.reg file: - Thanks to DaveXP for this tweak

CODE 

[HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\Desktop\General]"BackupWallpaper"="c:\\windows\\web\\wallpaper\\xppaper.jpg"
"Wallpaper"="c:\\windows\\web\\wallpaper\\xppaper.jpg"



Ofcourse you will need to replace "xppaper.jpg" with the actual file name of the wallpaper you wish to use, including its extention.

Note: I am not sure if you can use %systemroot%\\Web\\Wallpaper\\name_of_wallpaper yet, but i will try it out, and update this part of the guide.

i'm guessing those \\ things are only supposed to be 1 \ rite? tried it as the guide said and didn't work

#6 User is offline   ihaveabu 

  • Junior
  • Pip
  • Group: Members
  • Posts: 94
  • Joined: 21-August 04

Posted 26 August 2004 - 08:15 PM

ihaveabu, on Aug 26 2004, 07:45 PM, said:

jrzycrim, on Aug 26 2004, 07:17 PM, said:

Remove the GuiRunOnce stuff.

Remove these lines from cmdlines.txt:
bootcfg /RAW /A /Kernel=OEMKrnl.exe /ID 1
bootcfg /Timeout 0


Place your bootlogo.cmd in $OEM$

Add this line to cmdlines.txt:
"bootlogo.cmd"


I'm assuming your bootlogo.cmd contains the lines I told you to remove from cmdlines.txt

oh! quotes! i'm so dumb. i'll try it out. thanks.

now it doesn't boot. i see the boot screen, but windows doesn't start

#7 User is offline   jrzycrim 

  • Friend of MSFN
  • PipPipPipPipPip
  • Group: Members
  • Posts: 769
  • Joined: 17-March 04

Posted 26 August 2004 - 08:45 PM

Could be because you have the wrong kernel. Do you have a multi-processor or hyperthreading cpu? If so you need to be using a modified ntkrnlmp.exe.

What version of windows XP are you using? What version is your OEMkrnl.exe?

#8 User is offline   ihaveabu 

  • Junior
  • Pip
  • Group: Members
  • Posts: 94
  • Joined: 21-August 04

Posted 26 August 2004 - 09:08 PM

jrzycrim, on Aug 26 2004, 08:45 PM, said:

Could be because you have the wrong kernel. Do you have a multi-processor or hyperthreading cpu? If so you need to be using a modified ntkrnlmp.exe.

What version of windows XP are you using? What version is your OEMkrnl.exe?

i have a hyperthreading (2.4c)
can you tell me where i can get the one i need?
in installed a xp sp2 incorped.

#9 User is offline   ihaveabu 

  • Junior
  • Pip
  • Group: Members
  • Posts: 94
  • Joined: 21-August 04

Posted 26 August 2004 - 09:40 PM

some help please? i'm a noob at this.
@jrzycrim
is that in driver.cab? i think i might have it. after i mod it using resource hack, do i put it back in driver.cab or in the system32 folder?

#10 User is offline   jrzycrim 

  • Friend of MSFN
  • PipPipPipPipPip
  • Group: Members
  • Posts: 769
  • Joined: 17-March 04

Posted 26 August 2004 - 10:25 PM

It's in the I386 directory as well as driver.cab

In my I386 directory, there is ntkrnlmp.exe as well as ntkrnlmp.ex_.

I'm not sure how to mod ntkrnlmp.exe. I'm sure you can use resource hacker.

There are differences between sp1 and sp2 so I can't help you there. I think there's a thread for modding the sp2 kernel.

#11 User is offline   MCT 

  • MSFN Junkie
  • PipPipPipPipPipPipPipPipPip
  • Group: Members
  • Posts: 3,288
  • Joined: 19-May 04

Posted 26 August 2004 - 10:33 PM

also, when specifying a path via a .reg file u NEED 2 \\ 1 is for the path & the other magically disappears when imported, its basically so windows knows its a path (someone maybe able 2 explain it better, but u do need 2 \\)

#12 User is offline   ihaveabu 

  • Junior
  • Pip
  • Group: Members
  • Posts: 94
  • Joined: 21-August 04

Posted 26 August 2004 - 10:40 PM

jrzycrim, on Aug 26 2004, 10:25 PM, said:

It's in the I386 directory as well as driver.cab

In my I386 directory, there is ntkrnlmp.exe as well as ntkrnlmp.ex_.

I'm not sure how to mod ntkrnlmp.exe. I'm sure you can use resource hacker.

There are differences between sp1 and sp2 so I can't help you there. I think there's a thread for modding the sp2 kernel.

i don't have it in my i386. wth? and i modded the ntkrnlmp.exe. now do i still use the guide and rename it and put it in $$\sytem32? cuz i did that and trying installed in vmware, and it say system32\drivers\ntfs.exe or something is missing. wtf? wat does that have to do with this?

#13 User is offline   MCT 

  • MSFN Junkie
  • PipPipPipPipPipPipPipPipPip
  • Group: Members
  • Posts: 3,288
  • Joined: 19-May 04

Posted 26 August 2004 - 10:43 PM

did u MOVE the file? or copy it 2 the $$\System32 folder? :S

#14 User is offline   ihaveabu 

  • Junior
  • Pip
  • Group: Members
  • Posts: 94
  • Joined: 21-August 04

Posted 26 August 2004 - 10:47 PM

MCT, on Aug 26 2004, 10:43 PM, said:

did u MOVE the file? or copy it 2 the $$\System32 folder? :S

i opened drive.cab with winrar, and extracted ntkrnlmp.exe to desktop. moded it with resource hacker, saved, renamed to OEMKrnl.exe and copied that into the system32

#15 User is offline   ihaveabu 

  • Junior
  • Pip
  • Group: Members
  • Posts: 94
  • Joined: 21-August 04

Posted 26 August 2004 - 11:13 PM

it says ntfs.sys is missing. wtf?

#16 User is offline   MCT 

  • MSFN Junkie
  • PipPipPipPipPipPipPipPipPip
  • Group: Members
  • Posts: 3,288
  • Joined: 19-May 04

Posted 26 August 2004 - 11:28 PM

no need 2 repeat yourself

did u recompile the cab file?

also, do a search for this, its been answered i believe, search for ntfs.sys within the last 60days

#17 User is offline   ihaveabu 

  • Junior
  • Pip
  • Group: Members
  • Posts: 94
  • Joined: 21-August 04

Posted 26 August 2004 - 11:41 PM

MCT, on Aug 26 2004, 11:28 PM, said:

no need 2 repeat yourself

did u recompile the cab file?

also, do a search for this, its been answered i believe, search for ntfs.sys within the last 60days

well, i really didn't do anything to the cab file. just extracted it out of the cab and moded and put it in $oem$\$$\system32\
do i still need to do anything with the cab?

#18 User is offline   Alanoll 

  • CODE tags people, CODE tags!
  • Group: Patrons
  • Posts: 5,496
  • Joined: 25-September 03

Posted 27 August 2004 - 08:38 AM

what is it with people and changing the original kernel and then overwriting it.

Second, simply editing ntkrnlmp.exe and then putting it in $OEM$\$$\System32 (without renaming) won't work, as windows uses ntoskrnl.exe. the MP kernel is renamed to ntoskrnl.exe during install. Second, the ntfs.sys error is due to version conflicts with the kernel and files. Use the right kernel.

You could do what I do, look in the customize thread for the code I had, and have both kernels. VMware does NOT emulate the hyperthreading processor.

#19 User is offline   jrzycrim 

  • Friend of MSFN
  • PipPipPipPipPip
  • Group: Members
  • Posts: 769
  • Joined: 17-March 04

Posted 27 August 2004 - 01:12 PM

Doh! i forgot to mention that using ntkrlmp with a virtual machine would be a problem. Alanoll's script comes in handy in this case.

http://www.msfn.org/board/index.php?showto...=0&#entry108366

It will determine wether you have single or multple processors and use the correct kernel.

Modify ntoskrnl.exe and rename it OEMkernel.exe. Modify ntkrnlmp.exe and rename it DualKernel.exe. Place both in $OEM$\$$\System32. Use Alanoll's script in place of yours.

Now your custom kernel should work on both a virtual and real (hyperthreading) machine.

#20 User is offline   Alanoll 

  • CODE tags people, CODE tags!
  • Group: Patrons
  • Posts: 5,496
  • Joined: 25-September 03

Posted 27 August 2004 - 01:57 PM

But you STILL have to use the proper version of the kernel :P

And for the record, I suggest you run the batch from GUIRunOnce, and not cmdlines.txt. But that just might be personal preference. I like to see Windows start up before changing core system files :P

Share this topic:


  • 5 Pages +
  • 1
  • 2
  • 3
  • Last »
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy