theUnattender Posted November 1, 2004 Share Posted November 1, 2004 I am having a problem using this method with SP2 RC2. Everything installs and boots into Windows fine. Then I restart and I get an error saying ntfs.sys is corrupt or missing. I tried the fix that microsoft suggests and it still didn't work. Eventually I found out that it was a problem with the boot.ini. I left these commands out of my next attempt:bootcfg /RAW /A /Kernel=OEMKrnl.exe /ID 1bootcfg /Timeout 0and restarted without a problem. Now I don't have a custom boot screen though.same here, BUT ONLY, if i use a custom bootscreen, or an old one.if i EDIT the one that comes with SP2, and add my images to it, it works, BUT, the image starts showing fine, then, its colord go nuts, and the moving dots apear.i don't really know what the problem is, the colors change, like when you have a 24 bit bitmap, and save it as a 16 bits one.i tried using 16 and 24 bits bitmaps and the same thing happens.what should i do ?same problem here .. (on vmware though)as mentioned earlier in this thread maybe it has to do something with hyperthreading Link to comment Share on other sites More sharing options...
Schmendrick Posted November 10, 2004 Share Posted November 10, 2004 I am having a problem using this method with SP2 RC2. Everything installs and boots into Windows fine. Then I restart and I get an error saying ntfs.sys is corrupt or missing. I tried the fix that microsoft suggests and it still didn't work. Eventually I found out that it was a problem with the boot.ini. I left these commands out of my next attempt:bootcfg /RAW /A /Kernel=OEMKrnl.exe /ID 1bootcfg /Timeout 0and restarted without a problem. Now I don't have a custom boot screen though.same here, BUT ONLY, if i use a custom bootscreen, or an old one.if i EDIT the one that comes with SP2, and add my images to it, it works, BUT, the image starts showing fine, then, its colord go nuts, and the moving dots apear.i don't really know what the problem is, the colors change, like when you have a 24 bit bitmap, and save it as a 16 bits one.i tried using 16 and 24 bits bitmaps and the same thing happens.what should i do ?OK, I think I found the answer to our problems. The ntfs.sys corrupt error is caused by useing the wrong version of ntoskrnl.exe.For SP2 is should be version 5.1.2600.2180. If you use anything else, you will get that error.Now, as for the color problems....http://www.bootxp.net/ has a program that will take care of it for us (I havent tried it yet, but will soon)If you want to do it yourself this guy has a great guide.http://www.geocities.com/thejjoelc/XPbootcolors.htmlIt looks to be a royal pain in the tail section, especially if you have never done any hex editing (like me) but everything looks step by step, so Im gonna give it a try. Link to comment Share on other sites More sharing options...
bart of borg Posted November 11, 2004 Share Posted November 11, 2004 I have tried to implement a custom kernel install using gosh's method in my unattended DVd but, he does not say where I should put the file "bootlogo.cmd" to allow the winnt.sif changes to work. Where do I copy the file to?Now in cmdlines.txt or the GuiRunOnce section of your unattend file, put this:bootcfg /RAW /A /Kernel=OEMKrnl.exe /ID 1bootcfg /Timeout 0In your unattend file, make sure you have this:[unattended]UnattendMode=FullUnattendedOemPreinstall=YesOemSkipEula=YesI am using the GuiRunOnce method.......here is the relevant snippet of my .sif file:[Unattended] UnattendMode=FullUnattended OemSkipEula=Yes OemPreinstall=Yes OemPnPDriversPath="DRIVERS\ATI\Driver\2KXP_INF\DRIVERS\ATI\BIN;DRIVERS\ATI\Driver\2KXP_INF\B_18414;DRIVERS\ATI\Driver\;DRIVERS\ATI\WDM\WDM_XP;DRIVERS\ATI\WDM;DRIVERS\ATI" UnattendSwitch="yes" TargetPath=\WINDOWS DriverSigningPolicy=Ignore[GUIRunOnce] bootlogo.cmd Link to comment Share on other sites More sharing options...
borbomotsalo Posted February 11, 2005 Share Posted February 11, 2005 @Paul 365As you said the ntoskrnl is different....That is because you have a HT cpu an your Windows applies your multiprocessor Kernel...This is ntkrnlmp.exe renamed to ntoskrnl.exe during setup progress....Your solution is to modify all your Kernels in i386 folder and sp2.cab and re-apply them to your CD source....During your new setup windows will rename YOUR modified ntkrnlmp to ntoskrnl and everything is going to work fine....Regards ~`BorBoMoTSaLo~` Link to comment Share on other sites More sharing options...
MohamedYousri Posted February 22, 2006 Share Posted February 22, 2006 i wanna to know how to add lines to my cd Now in cmdlines.txt or the GuiRunOnce section of your unattend file, put this:bootcfg /RAW /A /Kernel=OEMKrnl.exe /ID 1bootcfg /Timeout 0In your unattend file, make sure you have this:[unattended]UnattendMode=FullUnattendedOemPreinstall=YesOemSkipEula=Yesi made my cd by Windows Unattended CD Creator and i have those java scripts RunOnceEx & konten in my winnt.sif file [GuiRunOnce]"%windir%\RunOnceEx.js"so how can i made that ??? Link to comment Share on other sites More sharing options...
T D Posted May 15, 2006 Share Posted May 15, 2006 Is the download link down? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now