Jump to content

jrzycrim

Member
  • Posts

    769
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by jrzycrim

  1. You're welcome. If it can be done, I'm not sure how. I've never seen a boot screen with the progress bar shifted horizontally.
  2. Just like an Oscar acceptance speech except you forgot to thank God and your parents... BTW, you're welcome for any help I may have provided.
  3. Great Job Astalavista! Pretty satisfying isn't it? I bet you're already starting on your next one.
  4. There are 5 locations (2 hex pairs each) which store the progress bar vertical position and height. Actually 3 for the position and 2 for position+height. The first 3 offsets for the vertical position: 37344, 3912D, 391B9 - Default values are 62 01 This actually translates to 0162 hex ; 354 decimal. That is the number of pixels from the top of the screen the p-bar is positioned at by default. The last 2 offsets are for the vertical position+progress bar height in pixels: 373C2, 391AF - Default values are 6A 01 Translates to 016A hex; 362 decimal. This is 354 (p-bar vertical position) + 8 pixel height. As an example, if you wanted to position the p-bar 200 pixels from the top: Convert 200 to hex: 00 C8 Swap the hex pairs C8 00. This is what you will write at the first 3 offsets. The p-bar's height is 8 pixels, so add 8 to 200, convert to Hex: 00 D0 Swap: D0 00. This is what you will write at last 2 offsets. The values at the first three offsets need to be between 0 - 631 (00 00 - 77 02 ) 631 because that is the very bottom of the screen minus the 8 pixel height of the p-bar. The values at the last two offsets need to be between 7 - 639 ( 07 00 - 7F 02) Just add 8 to the values you write to the first 3 offsets. 8 is the default height of the progress bar but this can be changed. I haven't tried it yet but if you want to try to change the height, the actual image will need to be changed and a different value for the second set of offsets will need to be used to reflect the new height. The progress bar can be moved completely off the screen but I haven't done this before. I assume you would write values which exceed the bottom position of the screen. If you go to far you will most likely crash when booting. The offsets for ntkrnlmp.exe are different: 3984C, 3B072, 3B08C and 398CA, 3B082
  5. You could try copying the cookie in Documents and Settings\username\Local Settings\Temporary Internet Files\. The filename should look something like this: username@google[1].txt There is also one in Documents and Settings\username\Cookies. I'm not sure which one you should use or if you should use both. You might also need to copy the Index.dat file which is in the same folder. I haven't done this so I don't know if it would work. Maybe somebody else will know more. Those settings should be saved in the cookie however.
  6. Bloodstalker: The first color is 00 00 00 not 15 1A 20. Use the go to feature of your hex editor: 75688 is the address the palette starts at or 79C08 for hyperthreading/multprocessor systems. The appropriate ntoskrnl will be in the system32 for either. That tutorial is a bit hard to read because it's all run together. For SP2, the only bitmaps you have to worry about are 1 and 8. Remeber, the SP2 kernel doesn't use the professional and home overlays.
  7. Once you convert your palette to the appropriate format it's just a matter of loading ntoskrnl.exe into your hex editor, going to the appropriate address and overwriting the old values with the new. I just grab a pencil and paper, look at the palette in PSP like I mentioned before, and then write down the values starting with the first color, add 00, go to the next color, add 00 and so on remembering to reverse the order of the hex pairs. There's a program called booteditor that makes this a lot easier but currently it doesn't support SP2. I think a new release is soon to come however.
  8. If you changed the palette of the custom ntoskrnl you are now editing then you will have to recolor the progress bar as well. When you finish the main image (bitmap 1), save the palette. I think you have already done that but I'm not sure. Grab Bitmap 8 from that custom ntoskrnl and load it into PSP. Load the palette you saved. If the image looks okay to you, then you can use it as is. If it looks funny (chances are it will) then just recolor it using the new palette that you loaded. I know it seems like a pain but once you get the hang of it, it's not so bad.
  9. Just go into reshacker, save bitmap 8. Load it into psp and then load the palette you saved from your custom image. You'll see what I mean when you load your new palette. Then just recolor it using the colors of the new palette. I find zooming the image and using a 1 pixel brush works well. It shoudn't take long as the image is pretty small. Save the image and use reshacker to replace the old image with the new.
  10. The problem is that the progress bar uses the same palette as the main image in the kernel. If you change the palette, then the original progress bar image is going to use that palette and will be colored differently.
  11. Some of the more recent submissions are for service pack 2. Just make sure that they include version 2180 for SP2. This dude who goes by the handle 'Hungherk' is submitting lots of SP2 kernels. There are others as well.
  12. I should add that you will need to design a progress bar image (Resource 8) using the same palette as your main image or else it will look weird. Just load that image into PSP and recolor it with the new palette.
  13. I forgot about those being in decimal. Well, there are two ways to go about this: 1) You can use the Calculator in windows (scientific view) and covert each number. what a pain in the a**. 2) You can go to Edit Palette in PSP and find the actual hex values for each color. They'll be at the bottom. remember, you will have to reverse the order for the custom kernel as Alanoll ponted out. Select the first color in the edit palette dialogue, reverse those hex pairs: example: if it's #FFCCEE you will need to use EE CC FF and then add 00 between each color. #F123C6 will convert to C6 23 F1 00, just to be clear...
  14. Try saving it as a PSP palette instead of a Microsoft Palette.
  15. Also, the offset for the palette is Hex address 75688. If you go directly to that address you will be at the start of the palette. Address 79C08 in the case of a multi-processor/hyper-threading kernel.
  16. For small Icons in the classic menu try this: Set small icons in your classic start menu, log out and then log back in. This ensures that explorer writes the settings to the registry. Export this key from your registry: [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\StuckRects2] The way I tested this was: 1) Set the start menu back to large icons. 2) Logged out and back in to ensure those settings were copied to the registry. 3) Killed explorer from Task Manager. 4) Launched a command prompt from Task manger: File > New task : cmd.exe 5) Imported the reg file from the command prompt I exported previously: Regedit /s regfile.reg or whatever. 6) Launched explorer from the command prompt. The small icons were back in the start menu so if you import this tweak from cmdlines.txt it should work. Extra note: The taskbar size is stored in that same key as well.
  17. It will work but you images will most likely look funny. You have to edit the palette which is stored in a different location in ntoskrnl.exe. See: http://www.msfn.org/board/index.php?showtopic=24286
  18. Try this: [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "Start_LargeMFUIcons"=dword:00000000
  19. There is a VB script in this thread that you can use to do this: http://www.msfn.org/board/index.php?act=ST&f=34&t=25196
  20. Yes, since you already have a cmdlines.txt file just add the "regedit /s regfile.reg" to it.
  21. You can try importing your reg file from cmdlines.txt: Place your reg file in $OEM$ make a new text file named cmdlines.txt in $OEM$ and place this in the file: [Commands] "regedit /s regfile.reg" At around T-13 during setup, the commands in cmdlines.txt will be executed; this is well before RunOnceEx entries are executed.
  22. Thanks for the tweak! I'm sure other people will find that useful.
  23. I don't see anything in your tweak file. Are you having a problem with the classic start menu or classic theme at startup? Post your winnt.sif.


×
×
  • Create New...