Edit setupreg.hiv

[dirtwarrior]

I want to edit setupreg.hiv

I import it into regedit, edit a few zeros in

Export it. Unload it from regedit. The size increases.

Can someone help?

dirt

[Veovis]

You want to edit setupreg.hiv or to copy to a .reg file ??

If you want to edit, you just load this file into regedit, modify then unload it. The setupreg.hiv file is modified.

If you want to work with a .reg file, load setupreg.hiv into the registry then export it.

[dirtwarrior]

I found regedt32 from 2k works better than regedit. I added regedt32 to xp by adding regedt32 from 2k along with a few dll's. Works good.

Edited March 23, 2006 by dirtwarrior

[Lemonzest]

I want to edit setupreg.hiv

I import it into regedit, edit a few zeros in

Export it. Unload it from regedit. The size increases.

Can someone help?

dirt

/me smells a warez monkey trying to bypass the Trial timebomb

Edited March 23, 2006 by Lemonzest

[dirtwarrior]

No way dude this is against the rules.

[nmX.Memnoch]

What exactly are you trying to edit?

[Veovis]

regedit of Windows XP is the total fusion of regedit and regedt32 of Windows 2000.

I'm OK with Lemonzest, if you edit setupreg.hiv, is to crack Windows.

If you want to add keys, you can use a .inf file as hive*.inf on the CD.

[dirtwarrior]

OK thanks

[Lemonzest]

what i meant by my comment (smells a warez monkey etc), was the ONLY time you need to edit setupreg.hiv is to crack it, i was not asking how too, sorry if you misunderstood

[Daemonforce]

I edit setupreg.hiv for several reasons:

Add a write filter

Force starting/installing services (Ipsec/Crypto)

Force/Merge product types (WINNT/LANMANNT)

Force desktop appearance

A lot of other fun stuff

I've never needed to edit the hive for cracking purposes. I think you're the warez monkey.

[nmX.Memnoch]

You don't need to edit setupreg.hiv to do those items. All you need are .reg files that get loaded during the GUI part of setup using CMDLINES.TXT. It's a much safer method and easier to manage.

[Daemonforce]

No it's not. If I use your method then it doesn't work. It's for a different scenario anyway.

[Veovis]

The hive in setupreg.hiv is use only during install in text mode. After all registry is loading from hive*.inf, so it's useless to modify setupreg.hiv. In graphic mode, there are nothing of setupreg.hiv in registry.

The best and easiest solution is to create a hivecst.inf by example (don't forget to add this file into txtsetup.sif and dosnet.inf next to other hive*.inf files), which is call in latest !

If you choose to use a .reg file, the file will loading after the first logon.

The advantage of hive*.inf files is they are loading with SYSTEM privileges during install.

Edited March 27, 2006 by Veovis

[skyhack]

Microsoft tells how to get extended functionality from Windows PE editing this hive http://www.microsoft.com/technet/technetmag/issues/2007/02/DesktopFiles/default.aspx, so how does it violate the EULA?

I'm sure most of the people on this forum know about the "Pro lite" hack, but that doesn't get you everything that XP Pro has, it just seems to open up some networking and remote functionality.

I haven't tried it, but this seems to be fundamentally different from, say, stealing and using a corporate key with the old setupp.ini edit.

Of course, if Microsoft sees this as a problem, I'd bet that WGA would pick it up and bust your chops for you.

http://www.msfn.org/board/style_emoticons/...t/whistling.gif

[dirtwarrior]

Post #1 and you bump an old thread. Well anyway hope you enjoy you stay here.