Jump to content

Viscon

Member
  • Posts

    37
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Poland

Posts posted by Viscon

  1. this should help if you want to start win2k3 setup out of folder renamed (from i386 to something else)

    open setupldr.bin with hex editor

    go to hex address 0x2060

    replace value 74 03 with EB 1A

    save file

    now you can edit setupldr.bin by replacing 5 occurences of i386 and 2 occurences of I386 with whatever you want,

    although i assume you've alrerady done so

    :rolleyes:

  2. most of the icons (quite a lot actually) you can change hacking shell32.dll.

    find shell32.dl_ file in I386 folder, and uncab it with this command in command prompt window:

    expand -r shell32.dl_

    now you have unpacked shell32.dll which you may open with Resource Hacker.

    on the left pane expand Icon Group folder, so you'll see all the icons to be changed.

    right-click any you want and choose Replace resource...

    or

    in the menu click Action and Replace Icon...

    this way you may also change bitmaps, cursors, and more...

    having changed your icons you have to re-cab shell32.dll with this command (command prompt too)

    makecab shell32.dll

    you got shell32.dl_ again but hacked with your icons,

    so copy it back to I386 folder overwriting an older one, and install XP.

    now your icons are set for good

    :whistle:

  3. yes, you can do this.

    actually i do this all the time.

    you just need to compress modified files and copy/overwrite them into nlited xp folder or iso image.

    (i use UltraIso.)

    let's say you want modified shell32.dll in your setup cd.

    open command prompt, navigate to folder where your new file is, and type:

    makecab shell32.dll

    you'll get a new compressed file shell32.dl_ ready to copy.

    ;)

  4. ever since i knew how to disable WFP i've kept it disabled, and never ever had problems with it.

    and it's been years = a long time.

    on the other hand though, i keep monitoring any changes occuring to my system (registry and files) with Ashampoo Unistaller Suite.

    that way i know in details what exactly happens here.

    that way i can also reverse any changes (including bad installations) that i find as not right.

    thus, WFP is completely useless for me.

    plus, of course, i can alter any system files lijke libraries myself - changing icons and bitmaps in order to customize my winxp my way.

    thnx nuhi for a nice and useful option in nlite.

  5. check winnt.sif file for this:

    [Shell] 
    DefaultStartPanelOff = No
    CustomDefaultThemeFile = "%WinDir%\Resources\Themes\xxx.theme"

    i might be wrong but something tells me that nlite misses the 1st entry under [shell].

    don't know for sure because i use another method to integrate my own theme.

    why? because nlite couldn't copy my wallpaper which is a part of my theme.

  6. no, no, no - destination partition can be smaller but big enough to keep data that is about to be cloned.

    i did cloning many times with ghost and i know that for sure.

    i would suggest to make sure the destination partition on 2nd hdd is primary and active.

  7. got the installer from retox, installed nlite...

    clean install on my second drive where nlite had never been installed before

    Bit Defender Plus v10, latest virii definitions, didn't alert at all during installation process,

    and while running nlite.

    same with The Cleaner - no alert about any trojan.

    same with AdAware SE Pro - nothing found.

    scanned again with Bit Defender with "deep scan", memory scan and for rootkits and malware - nothing wrong either.

    also - during setup and while running - nlite never attempted to call anywhere.

    my firewall didn't alert that it's trying to connect through internet.

    the only registry entry i found was "uninstall" nlite.

    no trace of "sudoku" and other suspicious entries.

  8. OK - enough is enough.

    retox, please upload the file that's supposed to be infected and i will scan it with bit defender plus v10.

    you say your bit defender alarmed positively, let's see what mine says then.

    you may upload the file on rapidshare and tell us a link.

    hopefully this test will finish all that embarrassing thread.

  9. looks like you must have missed something while hacking a file.

    did you try to change icons in there?

    you could delete some and haven't replaced them in a proper order.

    i hacked shell32.dll many times and it never failed.

    you just have to be very careful about the order icons are placed.

    try again with original file and make changes one-by-one.

  10. Bootable CD?What's the meaning of this? All XP CDs are bootable...

    Could you clearify?

    that's a response for your 1st post suggesting that 1.2RC has a broken engine and cannot make a bootable CD.

    of course XP cd is bootable and so should be nlited one as long as it has boot files and they're not corrupted.

    in my case nlited XP with 1.2RC is also bootable, so that's definitely not nlite issue.

    try again the whole process with original XP cd and see what happens.

  11. i myself tested nlited 2k3 and it installed and worked very well.

    this software had no probs (as i remember):

    adobe cs2 (photoshop, illustrator, indesign)

    ms office 2003 pro

    raxco perfect disk server

    macromedia 8 (dreamweaver, flash, fireworks)

    plus many games i can't recall now.

    just don't forget to check a link provided by boooggy.

  12. sounds like you disabled "beep" noise on errors.

    it's a bug that also disables startup and shutdown sounds.

    check for this key in registry:

    [HKEY_CURRENT_USER\Control Panel\Sound]

    "Beep"="yes"

    "ExtendedSounds"="yes"

×
×
  • Create New...