Jump to content
MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. ×

jrzycrim

Member
  • Posts

    769
  • Joined

  • Last visited

  • Donations

    $0.00 

Everything 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 if %NUMBER_OF_PROCESSORS%==2 goto DUAL echo No bootcfg /RAW "/Kernel=OEMKrnl.exe" /A /ID 2 goto End :DUAL echo Yes bootcfg /RAW "/Kernel=dualKrnl.exe" /A /ID 2 :End 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: 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. You downloaded the second one. You mean SP2 NTKRNLMP PRO? Open boot.ini with notepad and paste what you have here.
  5. You know, you need to exercise a little patience.
  6. 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] timeout=30 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS [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: Paste what you copied at the end: Edit the last line like so: 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.
  7. If you have a single processor system then don't use the ntkrnlmp.
  8. 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.
  9. That's why I pasted 'professional' and 'Home' in bitmap 1 of these kernels. SP2 doesn't use those overlays.
  10. Ah yes, these are for single processor systems. If you have a dual threading or multi-processor systetm, do not use these kernels. I'll upload a version using ntkrnlmp.exe.
  11. SP2 NTOSKRNL Home (962KB 7-Zip SFX) SP2 NTKRNLMP Home (992KB 7-Zip SFX) Boot Editor Files (9.52KB Booteditor Zip)
  12. 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.
  13. TaskBarXP is actually a value found in this key: [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Streams\Desktop]
  14. Yes, but you won't be able to make the progress bar follow that curved path because of the reasons Alanoll stated. Theoretically, it would be possible but from a practical standpoint it's not.
  15. For people having trouble with resolution problems in VMware, see this thread: http://www.msfn.org/board/index.php?showto...ndpost&p=160318 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.
  16. Sorry alanoll, I didn't mean to step on your toes.
  17. 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. 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.
  18. bootcfg /Timeout 0 Add that command to one your batch files.
  19. Pinned items are stored in this key: [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\StartPage] After you pin the items you want to the Start menu, log off and then back on and export that key to use in your reg tweaks. I did this from within vmware after testing my installation.
  20. No problem. The only reason I found it so easily was because I participated in that thread and knew what I was looking for.
  21. See this thread: http://www.msfn.org/board/index.php?showtopic=22555&st=0 I had to import the settings for icon arrangement during the second logon. I couldn't get them to work during the first logon unless I imported them into a customized ntuser.dat file. Anyway, the above thread explains it. Hope it helps.

×
×
  • Create New...