Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

Windows File Protection not accepting nlite-disk

- - - - - wfp nlite CD xp windows

  • Please log in to reply
38 replies to this topic

#26
bphlpt

bphlpt

    MSFN Addict

  • Member
  • PipPipPipPipPipPipPip
  • 1,915 posts
  • Joined 12-May 07
  • OS:none specified
  • Country: Country Flag

@whocares,

What you, I, Kel, or anyone else believe about the legality of using any particular piece of software, (or music or video for that matter), is totally irrelevant. What each of us chooses to use on our own machines in the "privacy" and "anonymity" (if such a thing truly exists these days) of our own homes is up to us and is no one else's business. Period. I'm sure Kel would agree with that as well. BUT ... In public, such as on this forum, we feel very strongly about abiding by the rules of wherever we are, and those rules are different depending on where you are. For example, I would assume your behavior in your bedroom with your beloved, or at a football game, or at the local bar, is probably different than when you are at church, unless you go to a very interesting church. :)  The same people behaving differently at different places does not make those people "bad" people or hypocrites, it just means they are following the rules of where they are.

Different forums have different rules. Here at MSFN, discussing warez of any kind, or helping anyone resolve problems that concern or are caused by warez, or even if it is proven that warez is in the picture in any way though not directly involved with the issue at hand, is not allowed. This also includes the use of "activators" of any kind to avoid the official activation methods for any software.  And it includes the distribution of any software except though officially approved channels. So no sharing a torrent link to a release of any version of MS Windows, even if the MD5 matches the one from Technet and no keys are shared.  Hiren's is a problem because of the included MiniXP as you surmised. Yes we know it is referenced in many places, but we don't allow it here. The use of any software in any way that is specifically forbidden in its EULA or terms of use, such as the use of nLite in a business application, non-profit or not, for example, is also not supported. We know all these rules are very strict and some may disagree with them since "everybody else does it", or whatever. Sorry, but those are the rules, and every member that signs up here agrees to them when they sign up. They are not up for debate or discussion. Anyone who disagrees and wants to pursue those kinds of topics is politely asked to do it elsewhere.  Those that continue to discuss it here anyway are banned.  There are other forums that have different rules, but you'll have to find those other forums on your own.
 
Problems and installation challenges of a mix of products on a variety of hardware are of interest to many here, and the solutions found can be of benefit to others.  If you can pose your questions so that the "forbidden" topics are not mentioned then the discussion can continue.  If any problem is specifically caused by the use of some "forbidden" software or one obtained through unapproved channels, then you are on your own to find the solution.  We will usually ask about the software involved, and if you disclose that it is one of "those", or if you refuse to say, then be aware that often we will simply tell you to get an officially released copy, try that, and then come back if you still have a problem.  Frustrating I know if you truly believe that the particular piece of software is not the issue, but there you are.
 
Personally, I think that the issues you are discussing in this thread and in http://www.msfn.org/...-multiboot-dvd/, are interesting and I would love to see the solution that you find that solves all the problems you ran into, if you can do it without mentioning any of the "forbidden" topics, of course. :)

 

Cheers and Regards


Posted Image



How to remove advertisement from MSFN

#27
whocares02

whocares02

    Junior

  • Member
  • Pip
  • 85 posts
  • Joined 21-March 14
  • OS:XP Home
  • Country: Country Flag

No problem with that. Don't remember mentioning anything legally diffcult after my topic got closed.

 

Not my fault Kelsenellenelvian now believes

 

A slightly modified disk from a supermarket isn't legal either...

 

 

I of course assume it just is. They sell computers (+software) regularly at specific dates in huge parts of the country. Imagine WalMart in US just would sell illegal XP-copys on some day before christmas, it was just scandalous - same here.  So no, I doubt my disk is legally problematic.

 

As to Hiren's: I use parted-magic-linux instead now  - just to calm down everybody. :yes:

 

Edit:

 

Oh forgot this:

I cannot find ANY proof of a hotfix changing the CDIDENT files either it doesn't happen.

 

It's strange for me too. I think...maybe....sfc always asks for the disk when file-versions don't match. It's possible it actually finds the Cd but not newest version of specific files.

 

As to my disk: I run some non-integratable Updates in RunOnceEx.cmd after XP's main-setup, silently. These updates are:

 

Windows-KB909520-v1.000-x86

Visual C++ Redistributable 2005

Visual C++ Redistributable 2008

.NET 3.5

WindowsXP-KB923191-x86

WindowsRightsManagementServicesSP2-KB917275

WindowsXP-KB901190-x86

SFU3-KB939778-X86

SFU35-KB939778-X86

IE7-Update KB938127-v2

IE7-Update KB947864

Script-Engine-Update

WindowsMedia6-KB925398-v2-x86

mp10setup.exe

 

...and a huge dotnet-Updatepack (about 400MB) with all updates for .NET 2, 3, 3.5 and 4. It needs about two hours for installation.

 

 

I just got the idea inserting the original cd upon sfc's request to see if it gets accepted. Sorry, up to now I just didn't get that idea.

 

Edit2:

 

Yes, the original CD works.


Edited by whocares02, 05 April 2014 - 09:39 AM.


#28
whocares02

whocares02

    Junior

  • Member
  • Pip
  • 85 posts
  • Joined 21-March 14
  • OS:XP Home
  • Country: Country Flag

Is it possible nlite didn't work cleanly when removing parts from windows (e.g. unneccesary drivers or features like windows-tour)? Didn't anyone suffered the same problem before? Disabling SFC is pretty hidden in nlite's wizard. It seems re-enabling it after installation isn't done by too many users.



#29
submix8c

submix8c

    Inconceivable!

  • Patrons
  • 4,466 posts
  • Joined 14-September 05
  • OS:none specified
  • Country: Country Flag

I just downloaded German Service Pack 3.

- fp40ext.in_ (fp40ext.inf) is incorrect (but see below for maybe not)

- ims.in_ (ims.inf) is incorrect

- layout.inf is correct <<-- leave it alone

Whether this is the case for the "original" SP2 Home "DEU" CD I don't know. If so, then it, too, is wrong. My "ENU" one is not wrong (nor is the ENU SP3 Package).

 

This link (that you gave) has erroneous instructions, as far as the string to change->to is concerned.

http://support.micro...kb/897128/en-us

The string "XP Professional" should be changed everywhere to "XP Home Edition" (where the link says just to "Home"). Oddly, in ENU "Full" SP3 Package, it appears to also have "XP Professional" in the "fp40ext.inf" file (it goes directly into the I386 folder), so I have my doubts that. The other two are in different folders in the SP3 Package and are different between the Home (IC folder) and Professional (IP folder) and should have that string changed only in the "ims.inf" file.

 

Regarding "ims.inf" cdtag values the should be as follows (near the end of the file):

cdtagfile     = "\win51ic"
cdtagfilei     = "\win51ic"
cdtagfilem     = "\win51mc"

spcdtagfilei     = "\win51ic.sp3" <-- in the case of the original CD, its should be "sp2" instead

These will be the values found in the "layout.inf" file and correspond to what you should have in the Root of the CD/DVD.. The original files (when opened with an Editor) will have a value of "Windows" and the integrated one (win51ic.sp3) will have nothing (empty). In other words, for the cdtag values above, change the "p" in the string to "c" (remainder of the strings are exactly the same).

 

Regarding the "fp40ext.inf" file (for "FrontPage 2000 Server Extensions") my XP Home SP2 has the file(s) in it as well as it being in the SP3 Package (with "Professional" as the string). In other words, why would you need to change it (since it's dropped directly into I386)? And why did the MS Article say to? :unsure:

 

For the two files above, as far as I can tell, only the "ims.inf" file needs changed and should be recompressed after fixing. The other two (again, as far as I can tell) do not need changed. The fixes described will apply to both the original CD/DVD file (if the values are incorrect) and the Slipstreamed CD/DVD file (which is definitely incorrect).

 

7-zip will open the compressed filename "ims.in_" and allow extraction. Move that file (after Slipstream) to a temporary folder for modification before extraction then modify as indicated above. There is an "ims.ca_" ("ims.cat") Catalog file as well but it appears to be common beteen Home and Professional and hopefully it won't affect installation with the modified INF file. Sometimes it matters - I don't know in this case. (Checksums, etc?) After modification, rename the "ims.in_" to (e.g.) "imsSAVE.in_" before recompression (see below).

 

To recompress the modified "ims.inf" to "ims.in_", open a CMD Prompt, change ("CD") to the temporary folder (the full path, e.g.: CD "C:\TEMPMOD"), enter the Drive Letter of the Folder (e.g.: C:) and enter the following:

makecab /D CompressionType=LZX /D CompressionMemory=21 ims.inf

The resulting replacement "ims.in_" should be copied (or moved, whichever) back to the I386 folder before final ISO creation.

 

Create the ISO (as you wish - I'm out of that subject), test, and burn (if you wish).

 

That's it, that's all, that's Microsoft for you.

 

HTH and good luck. I'm done here. :yes:


Edited by submix8c, 05 April 2014 - 12:42 PM.

Someday the tyrants will be unthroned... Jason "Jay" Chasteen; RIP, bro!

Posted Image


#30
mooms

mooms

    Hello world !

  • Member
  • PipPipPip
  • 302 posts
  • Joined 13-October 07
  • OS:Windows 7 x64
  • Country: Country Flag

@whocares02: For me the obvious and easy way to solve your problem is to start with a clean source, that mean grabbing a XP SP3 home German iso (that came originally) from MSDN.

MSDN hashes are public so you can have the assurance the source is clean. Then you can do the nLiting.



#31
whocares02

whocares02

    Junior

  • Member
  • Pip
  • 85 posts
  • Joined 21-March 14
  • OS:XP Home
  • Country: Country Flag

Hey listen, I know it's easy just to move all problems to the source. But no matter how often it got recommended already, I don't start from scratch again, not after two weeks. All problems up to now were solvable and not related to my disk. I'll try submix' attempt now - and if I fail, I still got a full-unattended, working and pre-configured XP with a minor bug in SFC. I actually can live with it.

 

Edit:

 

Guess what: On the vbox-machine running my testinstall, SFC is working now, after I inserted the original CD.

 

When I remove some helpfile from

\windows\help

and

\windows\system32\dllcache

for testing, SFC wants the CD. For some reason it accepts my nlite-disc now!

 

I have NO IDEA how and why! Opening ims.inf shows all cdtag-filenames uppercase (not sure if I did that modification). All strings still just read "Windows XP Home" without the word "Edition". I'll copy the files now and try them on a fresh nlite-install. Will post here upon success.


Edited by whocares02, 05 April 2014 - 03:27 PM.


#32
whocares02

whocares02

    Junior

  • Member
  • Pip
  • 85 posts
  • Joined 21-March 14
  • OS:XP Home
  • Country: Country Flag

There are files missing on my nlite-disk. I really believe that. The folder \windows\system32\dllcache contains 76 files only, after a fresh installation. When running

sfc /scannow

and inserting the original cd, windows immediately fills that folder. Up to now it contains over 900 files already and SFC's progress-bar is only at 25% right now. I'm sure SFC will accept the nlite-cd afterwards. I guess it was just a bad idea switching off SFC in nlite.

 

I'm trying submix' advice now, changing ims.in_ to recompile the iso for a next install.

 

in addition to his renaming of cd-id-strings in the extracted ims.inf, I changed win51ip2 to win51ic2 as well, since this seems to be the string for a 2nd-SP2-CD.

cd2name = "Windows XP Professional CD2"
cd2tagfilei = "\win51ic2";{locked}

My only question now is: How do I recompress with 7zip?

 

Edit:

 

Submix, I just tried renaming the cd-strings in an installed nlite-xp, in the way you described (just within \windows\inf\ims.inf). It's not working. SFC still complains, even after reboot. Are you sure it will work when editing ims.in_ in the iso? I (of course) did copy back all three files' original versions before modifying them in my running windows to ensure to make only described modifications.


Edited by whocares02, 05 April 2014 - 06:55 PM.


#33
mooms

mooms

    Hello world !

  • Member
  • PipPipPip
  • 302 posts
  • Joined 13-October 07
  • OS:Windows 7 x64
  • Country: Country Flag

Who said you have to restart from scratch ? just use a clean source and load your last session.



#34
bphlpt

bphlpt

    MSFN Addict

  • Member
  • PipPipPipPipPipPipPip
  • 1,915 posts
  • Joined 12-May 07
  • OS:none specified
  • Country: Country Flag

Is it possible nlite didn't work cleanly when removing parts from windows ... Didn't anyone suffered the same problem before? Disabling SFC is pretty hidden in nlite's wizard. It seems re-enabling it after installation isn't done by too many users.

  

There are files missing on my nlite-disk. I really believe that. ... I guess it was just a bad idea switching off SFC in nlite.


Well, yeah. :)

There might be a good reason that was hidden in the wizard. When most folks disable/remove SFC in nLite they don't plan on using it. Of course files will be missing if you try to re-enable it later. This is often true regarding any feature that you remove through nLite. Many features cannot be added back in later without practically starting over. Which is what folks have been advising you to do as well, though I understand your reluctance to do so.
 

Hey listen, I know it's easy just to move all problems to the source. But no matter how often it got recommended already, I don't start from scratch again, not after two weeks.


Keep in mind that you still might find more missing stuff later, such as a registry entry or something.  Just sayin'
 
Cheers and Regards


Posted Image


#35
whocares02

whocares02

    Junior

  • Member
  • Pip
  • 85 posts
  • Joined 21-March 14
  • OS:XP Home
  • Country: Country Flag

@mooms: It's not that easy: Nlite is always a bit capricious when integrating hotfixes and updates. E.g I found out it's a good idea cleaning the list and reimport all hotfixes to ensure nlite will integrate them, after loading the last session. Also some hotfixes need to be in special order. MSXML for instance needs to be at the end of the list, as well as IE7. Since Microsoft released a few hundred updates, I'm everytime glad when integration was successfull. I really don't wanna repeat that step if not neccesary.

 

 

There are files missing on my nlite-disk. I really believe that. ... I guess it was just a bad idea switching off SFC in nlite.


Well, yeah. :)

 

:lol: Thank you!

 

Edit:

 

Allright, I did it - running nlite again. This time with SFC enabled and IE8 included. Seems even IE8 isn't rejected this time, though there are problems with some of its updates. I put them in RunOnceEc.cmd to install them silently after setup. Curious already if SFC will work after test-install is complete (still in progress right now.)

 

Edit:

 

Yap, it's working! Opening

C:\Windows\System32\dllcache

already shows over 2000 files, directly after XP-installation. Removing a file from there and from windows-folder brings up CD-insert-request. nLite-disk gets accepted and files restored. I am using a modified ims.inf in addition. Hence I'm not sure if enabling SFC in nlite alon did the trick.

My ims.inf reads all cd-tag-names in capitals (because files on cd are uppercase as well).

 

cdtagfile = "\WIN51IP";{locked}

cdtagfilei = "WIN51IP";{locked}

cdtagfilem = "WIN51MP";{locked}

spcdtagfilei = "WIN51IP.SP2";{locked}

cd2tagfilei = "\WIN51IP2";{locked}

 

In addittion, all strings reading "Professional" are replaced with "Home".

 

 

 

Problem solved!


Edited by whocares02, 06 April 2014 - 05:12 AM.


#36
submix8c

submix8c

    Inconceivable!

  • Patrons
  • 4,466 posts
  • Joined 14-September 05
  • OS:none specified
  • Country: Country Flag

I am SOOOOOOO glad for you, even if you TOTALLY DISREGARDED my findings and instructions TO THE LETTER and report back (should I have translated to Deutsch for you? I took 2 years in HS. :yes: ).

 

I will now proceed to treat your posts as I have done with others of your mindest - disregard you back.

 

Good luck with the next problems you may encounter. ;)


Someday the tyrants will be unthroned... Jason "Jay" Chasteen; RIP, bro!

Posted Image


#37
whocares02

whocares02

    Junior

  • Member
  • Pip
  • 85 posts
  • Joined 21-March 14
  • OS:XP Home
  • Country: Country Flag

:lol: SORRY, didn't see your answer up to now! It's not true what you say!  :angel   I tried your attempt. I modified my ims.inf exactly as described by you without success. Doing the same within the iso was not possible for me. :whistle: You didn't tell me how to recompress ims.in_ with 7zip. :D I'm sure XP don't accept .7z-files - so some other option must be chosen. With just moving back the modified file into the archive, 7zip complained something alike "operation not possible".


Edited by whocares02, 06 April 2014 - 02:50 PM.


#38
dencorso

dencorso

    Iuvat plus qui nihil obstat

  • Supervisor
  • 5,752 posts
  • Joined 07-April 07
  • OS:98SE
  • Country: Country Flag

Donator

7zip cannot, but cabarc sure can.



#39
Kelsenellenelvian

Kelsenellenelvian

    WPI Guru

  • Developer
  • 8,688 posts
  • Joined 18-September 03
  • OS:Windows 7 x64
  • Country: Country Flag
You could also just delete the original and put the uncabbed one in there it would still work

Edited by Kelsenellenelvian, 06 April 2014 - 05:48 PM.






Also tagged with one or more of these keywords: wfp, nlite, CD, xp, windows

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users