• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
Sign in to follow this  
Followers 0
caps_buster

Windows 2000 registration CD key

34 posts in this topic

JoinDomain is wrong unless you are actually JOINING TO A DOMAIN SERVER! Are you? Did you MISS that in the DOC??? What's your intent? to cause it to FORCE it to allow adding New Users?

As far as the DOC, even that Atlantis software probably has a way to change the View. It does the SAME THING in Word until you change it. ;)

Why the heck don't you start with what I gave and add to it accordingly? WHY are you going an entirely different route? WHY are you bothering us if you refuse to "listen"? I TOLD you to read the DOC in the first place, didn't I? And as far as REF.CHM, YOU HAVE THAT TOO inside of you XP-SP1a, DON'T YOU????

Dude, you're on your own from here on out. :yes:

0

Share this post


Link to post
Share on other sites
1 - jaclaz gave you an alternative.

Not for windows, so, no alternative at all.

Well you will be the first one that cannot use xchm on Windows:

http://xchm.sourceforge.net/

Originally written for UNIX systems (Linux, *BSD, Solaris), xCHM has been since ported to Mac OS X and Windows.

Now, if you are not capable of getting (from the above) to here:

http://sourceforge.net/projects/xchm/

and from the above to here:

http://sourceforge.net/projects/xchm/files/?source=navbar

and from the above click on either of:

Download xchm-1.19win32.zip (906.5 kB)

or get here:

http://sourceforge.net/projects/xchm/files/xCHM%20for%20Win32/

and click on:

xchm-1.19

you might want to take a course on "navigating the internet".

jaclaz

0

Share this post


Link to post
Share on other sites

Not need the course on how to navigate thru the internet, just need a course on how to make the WinXP SP1.0a accept modified TXTSETUP.SIF and LAYOUT.INF files. It does refuse to accept these modified by me.

0

Share this post


Link to post
Share on other sites

Not need the course on how to navigate thru the internet, just need a course on how to make the WinXP SP1.0a accept modified TXTSETUP.SIF and LAYOUT.INF files. It does refuse to accept these modified by me.

Maybe it is possible that you modified them "wrongly". :unsure:

jaclaz

0

Share this post


Link to post
Share on other sites

jaclaz - you are quite possible right. I'm a novice in the windows modification and a stubborn one, so I have to learn all by myself. Usually a trial&error (or terror?) :) However I would not refuse to accept some help out there, lol.

For example I was fairly sucesfull in the Windows 2000 SP4 install modification - now it support the LBA drives AND I did not need to enter the CD key. That is IMHO great (at least for me) and there is only a very slight annoyance - and that it that I failed to disable the FireWire 1394 driver to be loaded in the whole beginning of the installation of W2k. This is really a minor thing, yet the last thing I wanted to accomplish.

If you can check out these Win2k SP4 LAYOUT.INF and TXTSETUP.SIF files:

layout+txtsetup.zip

..and please tell me, what can I disable to kill the unnecessary loading of the FireWire 1394 driver on the install initialization to make it faster, that would be great. Because I can attempt it myself, but that probably not end up well, like the WinXP SP 1.0a case.

I'm going to meddle with the XP later, lol. I never give up on the mods, till they are done.

PS. It probably is quite easy (not to load the FireWire 1394 crap) - in TXTSETUP.SIF, there is the "[busExtenders.Load]" and there is the "sbp2port = sbp2port.sys" and this is later defined as "sbp2port = "... IEEE 1394 SBP2 Storage Port", files.sbp2port,sbp2port" ... so just removing this line cause this bus extender are not being loaded on the Win2k SP4 install startup.

Gotta test this idea in reality :)

PS2. And indeed it work! So using quite simple WINNT.SIF file (without any Unattended.txt file!) it give me all I wanted: not need to enter the CD key, skip EULA and default network components installed as well, as not waiting for many keys during install - hooray!

[Data]AutoPartition=0MsDosInitiated="0"UnattendedInstall="Yes"[Unattended]OemSkipEula=YesFileSystem=*DriverSigningPolicy=Ignore[UserData]ProductID="xxxxx-xxxxx-xxxxx-xxxxx-xxxxx"[Networking]InstallDefaultComponents=Yes[Components]msmsgs = Offmsnexplr = Offfreecell = OffAutoUpdate = OffCertsrv = OffCertsrv_client = OffCertsrv_server = OffChat = OffDeskpaper = OffDialer = OffDtcnetwork = OffFax = OffFp_extensions = OffFp_vdir_deploy = OffHearts = OffHypertrm = OffIEAccess = OffLicenseserver = OffMedia_clips = OffMedia_utopia = OffPinball = OffPop3Admin = OffPop3Service = OffPop3Srv = OffRootautoupdate = OffSpider = OffTemplates = OffTerminalServer = OffTSWebClient = OffZonegames = Off

...now is time to look on the WinXP SP 1.0a :D

Edited by caps_buster
0

Share this post


Link to post
Share on other sites

So, jaclaz, there are the Win XP SP 1.0a czech files LAYOUT.INF and TXTSETUP.SIF.

Both with their original state and my modified state.

What I did wrong? I just cleaned out the files, removing empty lines and stuff and removed many of the ".Load" files to get the install rid of many of the unwanted files. Is this that big crime, so the install should crash, as it does?

WinXP SP1.0a CZ layout+txtsetup files.zip

0

Share this post


Link to post
Share on other sites

Which exact kind of "crash" do you get?

Can you describe what actually happens?

At first sight you are editing the file in a "semi-random" way :w00t:, in the sense that you are removing just an occurrence of *something* without thoroughly checking the whole file for other occurrences of the "same" *something* (IF and how this will affect the result cannot say)

Still at first sight, removing ksecdd.sys may be not a smart idea. :unsure:

I guess you would find interesting info and useful tools here /which you may want to re-read):

http://www.msfn.org/board/topic/106964-forgotten-setup-secrets-revealed/

and:

http://reboot.pro/topic/3951-forgotten-setup-secrets-revealed/

http://reboot.pro/topic/3960-ninf/

ninf is not that bad :), and AFAICR once the modified setupapi.dll issue has been finally solved:

http://www.msfn.org/board/topic/162523-winxp-sp10a-czech-setupapidll-hack/

http://www.msfn.org/board/topic/139018-setupapidll-and-winxp-sp10a/

there is no particular difference between SP1.0a and later servicepacks (or original "Gold" release)

jaclaz

0

Share this post


Link to post
Share on other sites

I tried to describe it as well, as I can there:

http://www.msfn.org/board/topic/162523-winxp-sp10a-czech-setupapidll-hack/

...but if the ksecdd.sys is really required (it was not in W2k file, so I removed it) as part of the core, then it might explain all the issues I having. Hence new test must be done with the ksecdd.sys back in the Filesystems.Load section of TXTSETUP.SIF.

So, back to testing - thanks for the first sight! Now I removed also the "_x" to prevent checking the files, so we see, if the install can work with modified files - that is the goal.

0

Share this post


Link to post
Share on other sites

I tried to describe it as well, as I can there:

http://www.msfn.org/board/topic/162523-winxp-sp10a-czech-setupapidll-hack/

...but if the ksecdd.sys is really required (it was not in W2k file, so I removed it) as part of the core, then it might explain all the issues I having. Hence new test must be done with the ksecdd.sys back in the Filesystems.Load section of TXTSETUP.SIF.

So, back to testing - thanks for the first sight! Now I removed also the "_x" to prevent checking the files, so we see, if the install can work with modified files - that is the goal.

NO, that was BEFORE you managed to get the SETUPAPI.DLL "hacked".

It is assumed that once you had it hacked you already tried to install with a NON modified TXTSETUP.SIF and that you were successful AND that you already tried to install with only a single, trivial, non-show-stopper edit of TXTSETUP.SIF and that you were successful.

This would excludde that ti s anything wrong in the patch.

Now you should have different symptoms or a different "crash" (namely a BSOD of some kind, most probably) than:

When installing, it keep getting stuck on the message that the Win install file is wrong and it's signature is missing. It give this code of error: 800b0100 ...

When reporting a problem, do always follow the standard litany:

http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/problem-report-standard-litany.html

it will be easier for everyone :). (and no, "install crashes" is NOT a description - or an accurate enough one - of what happens and that you see, remember how we cannot see what is happening on your PC and we have to base any suggestion on your descriptions of what happens).

jaclaz

Edited by jaclaz
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.