Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by jrzycrim

  1. You can use the same unattended cd for both.

    Here's a batch file that Alanoll posted a while back:

    bootcfg /copy /D "Windows XP Professional" /ID 1
    echo No
    bootcfg /RAW "/Kernel=OEMKrnl.exe" /A  /ID 2
    goto End
    echo Yes
    bootcfg /RAW "/Kernel=dualKrnl.exe" /A  /ID 2
    bootcfg /Timeout 0
    bootcfg /Default /ID 2

    Copy the above into notepad and name it boot.cmd or whatever you like. Place both the single and dual kernels in the system32 directory.

    Place the cmd file in $OEM$ and call boot.cmd from cmdlines.txt. It will detect which type of processor you have and write the appropriate kernel into the boot.ini. Just make sure the names used in boot.cmd are the same as the filenames you used for the kernels.

    This way, the same CD will work in VMware/Virtual PC and a hyper-threading or single processor system.

  2. I don't have one without Service pack 2 but I can throw one together fairly quick. Tomorrow maybe.

    For autologon, try this reg file:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]"AutoAdminLogon"="1"



    Copy and paste that into notepad, put in your username and password, save it as "logon.reg". Use the quotes around the filename when saving it.

    Double click on the new reg file to merge it into the registry.

  3. No, not off hand. When you extracted the kernel you downloaded, did you rename it Newkrnl.exe and put that in your windows\system32 directory? Make sure you didn't name it Newkernl.exe.exe by mistake.

    Which kernel did you download? If you have a hyperthreading system, you need SP2 NTKRNLMP PRO.

    If you have a system with a normal, single processor, you need SP2 NTOSKRNL PRO.

  4. hhmmm, sorry jrzycrim but i don't really understand what to do.  can you or someone in this forum give me a detailed set of instructions i can follow to make my XP PRO SP 2 boot up screen look like normal with the version under Windows XP.  I will be using Paint Shop Pro 9 or Adobe Photo Shop (if someone has photo shop for adobe, please help me with that one) THANKS a lot

    Let's make this simple. Download the appropriate Kernel. Extract it. Rename it to newkrnl.exe. Copy it to Windows\system32\

    Open a command prompt, enter:

    attrib -r -s -h boot.ini

    notepad boot.ini

    In notepad, you should see something like this.

    [boot loader]
    [operating systems]
    multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP Professional" /fastdetect

    Don't worry if it's not exactly the same.

    Select and copy the last line:

    [boot loader]timeout=30


    [operating systems]

    multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP Professional" /fastdetect

    Paste what you copied at the end:

    [boot loader]timeout=30


    [operating systems]

    multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP Professional" /fastdetect

    multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP Professional" /fastdetect

    Edit the last line like so:

    [boot loader]timeout=30


    [operating systems]

    multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP Professional" /fastdetect

    multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP Test" /fastdetect /kernel=Newkrnl.exe

    Hit CTRL-S to save and reboot. You will now have a boot menu. Select Windows XP test and see if the new kernel works. If it does, you can edit the boot.ini file and remove the original OS entry:

    multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP Professional" /fastdetect

    If it doesn't work, then you still have the option to reboot with the original kernel. This is the safe method as opposed to just replacing ntoskrnl.exe outright.

  5. Well, I used Paintshop Pro and Reshacker. I ripped the home and professional overlays as well as the main bitmap from an older SP1 kernel. I loaded all the images into PSP and loaded the default palette. I simply pasted 'Home' and 'Pro' onto the main bitmap and changed the copyright date. Loaded an all-black palette into all the images and saved them. Used Reshacker to load the images back into the sp2 kernel. Oh, I almost forgot, I grabbed the green progress bar from the older kernel to use for the new home version. Makes it look like the older home edition booting. Loaded the same images into the ntkrnlmp versions.

    bucketbuster, if your using booteditor, just download the booteditor files. Make a folder in your booteditor folder and place XPSP2Pro.bootscreen in that folder. Run booteditor. On the left, you should see the name of the folder you just created. Double-click on that, then select the bootscreen. CLick test. Look in your system32 folder for a filed called newboot.exe. That's the newly created kernel.

  6. Sorry folks. I haven't been around much since I started this thread. They've been keeping me busy at Ozzu.com as a moderator. There didn't seem to be much of a demand at the time and honestly, I forgot about it. :)

    The first link is the SP2 ntoskrnl.exe(2180) for singe processor systems. The second link is the kernel for hyperthreading/multiprocessor systems. The third link is for the files which can be used to compile your own kernel with booteditor. These are idependant of the kernel type and will work for single or dual.

    SP2 NTOSKRNL PRO (970KB 7-Zip SFX)

    SP2 NTKRNLMP PRO (992KB 7-Zip SFX)

    Boot Editor Files (9.73KB Booteditor Zip)


    I'll post the Home version soon.

  7. For people having trouble with resolution problems in VMware, see this thread:


    On the third page, there is a download link for the VMware video drivers. You can incorporate those into your installation and won't have to worry about using a command to change the resolution; the appropriate info in your winnt.sif will suffice.

    Of course, this doesn't address resolution problems you may encounter during installation on a real system. That will depend on your real video drivers.

  8. net user Dyne -------- /add

    If your password is longer than 14 characters, net user will prompt you with a warning. This may be stalling your installation at T-12; if your password is longer than 14 characters.


    You cant put a backslash in fron of %systemdrive%.

    Test it by opening Start>Run and typing in both "\%systemdrive%" and "%systemdrive%"

    You will get an error message when you use the one with the backslash.

    The extra backslashes are necessary when you need quotation marks to be written as a part of the path. This is the case when the path includes spaces.

  • Create New...