• 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
andros

Is nLITE installed by it in my WXP?

24 posts in this topic

I have used nLITE to integrate SATA in WXP's CD.

But I now discover that nLITE is installed and conceal in the PC.

What does mean this?

post-362090-0-56384600-1347896212_thumb.

sysoc.inf.TXT

0

Share this post


Link to post
Share on other sites

It's the result of integration. nLite uses NLITE.INF to remove/modify ("tweak") components. nLite itself is not actually "installed". Why it's showing I'm not sure - the "HIDE" in SYSOC.INF should have prevented that. Did you see the "description"? You apparently did some of that.

edit - You DID use the latest from http://www.nliteos.com right?

Edited by submix8c
0

Share this post


Link to post
Share on other sites

I know what your issues are (just from reading your sysoc)

Your source is NOT clean and original...

Your source has a beta SP applied to it.

Your source is MOST likely warez.

Also whay in the first place are you trying to hide that nLite was used? It is not to be used for business uses anywaysd so what does it matter at home?

0

Share this post


Link to post
Share on other sites

Excuse me, windows is original.

Some useful suggestion?

0

Share this post


Link to post
Share on other sites
I know what your issues are (just from reading your sysoc)

Your source has a beta SP applied to it.

I will correct that - Your SOURCE is BETA (Specifically RC2)! All SYSOC.INF of XP-32-bit from RTM and up start at "5.1.2600.0" (RTM). Yours SPECIFICALLY STATES "5.1.2535.0". All Released Service Packs since RTM (AFAIK) also conform to the actual CD's. I would call that "suspect"... Shall I illegally download it to prove it (yes, I found it)? I might ALSO suggest that Beta keys will not (AFAIK) work with RTM and up, so have at it, my friend. ;)

Although... I guess you COULD "hack" it and make it work, also HIGHLY illegal.

Besides the fact that I answered your question AND wondered about the "HIDE" part... Searching the Internet on

nLite "SYSOC.INF"

even suggests removing it (as jaclaz too suggested), although "tweaks" will "break" it since it's already been applied.

edit - OHHHH!!!! Found this. Interesting...

Prior to 2542 testers were able to use their product key for multiple installations, which of course makes sense for beta testers but isn't what Microsoft has planned for the finished product.
Still, looks like "hacks" would be required... Edited by submix8c
0

Share this post


Link to post
Share on other sites

Ok here is the beef in a full rundown BEFORE you try to convince us your source is original and genuine:

(sysoc from a msdn gold xp source)

[Version]

Signature = "$Windows NT$"

DriverVer=07/01/2001,5.1.2600.0

[Components]

NtComponents=ntoc.dll,NtOcSetupProc,,4

WBEM=ocgen.dll,OcEntry,wbemoc.inf,hide,7

Display=desk.cpl,DisplayOcSetupProc,,7

Fax=fxsocm.dll,FaxOcmSetupProc,fxsocm.inf,,7

NetOC=netoc.dll,NetOcSetupProc,netoc.inf,,7

iis=iis.dll,OcEntry,iis.inf,,7

com=comsetup.dll,OcEntry,comnt5.inf,hide,7

dtc=msdtcstp.dll,OcEntry,dtcnt5.inf,hide,7

IndexSrv_System = setupqry.dll,IndexSrv,setupqry.inf,,7

TerminalServer=TsOc.dll, HydraOc, TsOc.inf,hide,2

msmq=msmqocm.dll,MsmqOcm,msmqocm.inf,,6

ims=imsinsnt.dll,OcEntry,ims.inf,,7

fp_extensions=fp40ext.dll,FrontPage4Extensions,fp40ext.inf,,7

AutoUpdate=ocgen.dll,OcEntry,au.inf,hide,7

msmsgs=msgrocm.dll,OcEntry,msmsgs.inf,hide,7

RootAutoUpdate=ocgen.dll,OcEntry,rootau.inf,,7

IEAccess=ocgen.dll,OcEntry,ieaccess.inf,,7

Games=ocgen.dll,OcEntry,games.inf,,7

AccessUtil=ocgen.dll,OcEntry,accessor.inf,,7

CommApps=ocgen.dll,OcEntry,communic.inf,HIDE,7

MultiM=ocgen.dll,OcEntry,multimed.inf,HIDE,7

AccessOpt=ocgen.dll,OcEntry,optional.inf,HIDE,7

Pinball=ocgen.dll,OcEntry,pinball.inf,HIDE,7

MSWordPad=ocgen.dll,OcEntry,wordpad.inf,HIDE,7

ZoneGames=zoneoc.dll,ZoneSetupProc,igames.inf,,7

[Global]

WindowTitle=%WindowTitle%

WindowTitle.StandAlone="*"

[Components]

msnexplr=ocmsn.dll,OcEntry,msnmsn.inf,,7

[strings]

WindowTitle="Windows Professional Setup"

WindowTitle_Standalone="Windows Components Wizard"

PLUS there are CLOSE TO A dozen missing and\or added lines between the 2.

nLite has not added itself in that style (Without the hide) in many years...

0

Share this post


Link to post
Share on other sites

Some useful suggestion?

Why don't you simply remove it? :unsure:

http://www.mvps.org/ecvogel/kb/XP_remove_progs.htm

jaclaz

This does not work for nlite:

Open The Add or Remove Programs in Control Panel.

Click on Add/Remove Windows Components. You will now see options for Accessories and Utilities (the programs in the Accessories menu on the Start panel), MSN Explorer and several other components.

Remove the check next to the component to remove it or check it to install it from your XP CD.

0

Share this post


Link to post
Share on other sites

DUDE seriously you are using a illegal disk!

That is against the rules here.

STOP!! (A friendly-ish warning before a mod bans you).

0

Share this post


Link to post
Share on other sites

Here I show nLITE.inf of another original WXP sp3, that also I used nLITE

Excuse to me, that some your explanation I do not understand.

I will ask for help.

I believe it is a good idea that the author or someone explains what does this nLITE.inf.

And why it is not possible to remove nlite from components of W .

And, that half a world, we are not "zombies"

nlite.inf.TXT

0

Share this post


Link to post
Share on other sites

DUDE seriously you are using a illegal disk!

That is against the rules here.

STOP!! (A friendly-ish warning before a mod bans you).

I can go to your every in order that you see it.

And in addition to say to you that MS has considered it to be original.

0

Share this post


Link to post
Share on other sites
Here I show nLITE.inf of another original WXP sp3, that also I used nLITE
Nope, dude... it's the "LAST SESSION.INI" that tells what ELSE was modified.

Right at the top of this screen:

If you are having issues with Windows after removing components and have come to ask for help, please attach (not paste) your Last Session.ini file to your post to facilitate quicker assistance.

Excuse to me, that some your explanation I do not understand.

I will ask for help.

I believe it is a good idea that the author or someone explains what does this nLITE.inf.

It's sole purpose is to "kick off" the remainder of the "modifications" (see above RED). If you do NOT have the above file - IT IS SUSPECT! What you have provided (NLITE.INF) does NOT EVEN TELL that it's from "original WXP sp3" - it could be from ANY nLited source! Provide it or be quiet!

And why it is not possible to remove nlite from components of W .

And, that half a world, we are not "zombies"

Repeat - nLite is NOT installed! An nLited XP is installed! Review the nLite FAQ. Nuhi (the creator of nLite) is no longer available and there will be NO explanation of the "details" of this PROPRIETARY software except what may be "gleaned" from this and whatever else has been "discovered". The Source for the Program is "closed" and we DO NOT have it OR do we have Nuhi's notes and private documentation. Use it or not - Period.
And in addition to say to you that MS has considered it to be original.
So... you were a Beta Tester?
0

Share this post


Link to post
Share on other sites

Spanish SP3 source (NOT the one you originally posted)? You've removed quite a few components, which is your option. Otherwise.... so what?

The first file you posted (SYSOC.INF) still indicates a Beta (Pre-RTM) source and the entry

nLite = ocgen.dll,OcEntry,nLite.inf,HIDE,7

specifically says that it's "HIDE" so it should not have shown in ADD/REMOVE. The second file you posted (NLITE.INF) will still tell nothing. As has been stated, NLITE.INF only "polishes off" the Install (via NHELPER program) and sets some Registry Entries. NLITE IS NOT INSTALLED!!!

I'm really not sure WHAT you expect as "answers". If the "LAST SESSION" files are from an nLite Session against a FULL UNALTERED SPANISH XP-SP3 Source (all dates of Files/Folders EXACTLY THE SAME, unless an OEM-altered Installation CD) then (again) so what... BUT if they are from the Source, then it's a "bogus" Source (already nLite'd) and components have been removed.

To change to a Spanish Source you could to start with (e.g.) an English Source and apply a Language Pack. OR you could obtain a Spanish source (as well as other languages) as you appear to have (now).

That is all there is to it. You have your answers.

0

Share this post


Link to post
Share on other sites

1) I have 1 DELL DIM 9100, with WXP MC sp2 (English) (original?), installed with a copy DVD facilitated by DELL.

2) I have 1 DELL DIM E520, with WXP sp3 (Spanish) (original), installed with a CD bought distributor MS.

1) I used nLITE to remove languages, keyboards, games, and some thing plus.

a) NLITE, it is possible to see "HIDE" in the PC.

B) When I remove "HIDE", then I see nLITE in " adding / removing components of W ".

And when I unmark "nLITE", and I execute, nLITE remains.

2) I used nLITE to remove languages, keyboards, games, and some thing plus. I have added SATA to the CD.

And in this PC the same things happens.

3) That I want?

So, to know what it does "nLITE" as component of W, that in addition I cannot remove.

0

Share this post


Link to post
Share on other sites

@!#$%^&*()_!!!!!!!!!!!!

IT DOES NOT REMOVE!!!! There is NO FACILITY TO "DELETE" IT! NOTHING IS "INSTALLED"!!!! NOTHING TO "REMOVE" except that STUPID ENTRY!!!!

Look inside OTHER INF FILES! THEY SELF-DELETE!!!

Do you REALLY want it to no longer show? REMOVE THAT LINE FROM SYSOC.INF!!!!!! Removing "HIDE" will MAKE IT SHOW!!!

LOOK INSIDE YOUR NLITE.INF - IT DOES WHAT I SAID IT DOES!!!! Learn a little about INF files and how they work. THIS IS NOT THE TOPIC FOR THAT!!!!

JEEZ, dude, how many times to I have to tell you????

Use nLite or NOT!!! I don't care anymore!

0

Share this post


Link to post
Share on other sites

Chill, Submix ! Read forum rule 11 and 7b.

0

Share this post


Link to post
Share on other sites

I sit you not understood the own difficulty of our different language.

Besides the technical problem.

I have not had intention of being a nuisance since it seems that someone says

Only I can begin the fault.

And to ask for clemency

Thank for your help

0

Share this post


Link to post
Share on other sites

@Ponch - understood :blushing:

@andros - granted :yes:

@anyone - PLEASE don't pester for an answer already given as it sounds like an MSNBC Political Interview and the same answer will be provided ;)

re: Rule#11 - I have stated (once) before than MANY times I use caps as they are much more expedient than swipe/click/click/click OR extra leading/trailing characters... I am by nature a "Mainframer" and CAPS were heavily used on a 3270 TSO/ISPF screen interface to COBOL/PLI/ASSEMBLY/FORTRAN (etc) coding... Force of habit, especially since I'm now missing a tip of a finger. Bear with the NORMAL usage of it please - beyond that it may well be "other than" (as in :realmad: ).

Edited by submix8c
0

Share this post


Link to post
Share on other sites

First, please forgive me if I have misunderstood how any of this works since I do not use nLite.

@andros - If I understand your question, after using nLite on two different PC's, if you remove "HIDE" in the line in SYSOC.INF, then you see nLITE in "adding / removing components", but if you try to uninstall or remove nLite it doesn't go away and you want to know why and how to get rid of it, do I understand your question? Have you searched in Program Files to verify if the nLite executable is actually there? If the nLite executable is not on the PC, then it is not installed.

@submix8c - I've never used nLite, but from what I've read about it and from reading your answers here, even though nLite is used in building the image that is installed, nLite is not actually installed on the resulting PC, so the nLite entry in "adding / removing components" is just a phantom entry, only visible if the "HIDE" is removed, which is why the "HIDE" was put there in the first place, is that correct? If andros does not want the phantom entry there he should just leave the "HIDE" alone or eliminate the entire line in SYSOC.INF, are those his only options? Is there no other way to eliminate the nLite entry after the fact through the registry or something?

Perhaps someone should contact Ricktendo64 or someone else who might be willing to lend a hand with translation to/from Spanish since that seems to be part of the problem in this thread?

Cheers and Regards

0

Share this post


Link to post
Share on other sites

Nope... the "Components" section of the INI indicates "removed" components. As stated, the nLite.inf only "adds" registry entries and kicks off "nhelper" as a "runonce". I've already done a "test run" of nLite with a similar scenario to ensure I was correct in my "assumptions" (inspecting the "outcome"). I generally remove nothing since IMHO it gains little and only slip updates/drivers and maybe create a User - "KISS" method. In the OP's case they (apparently) used a Dell OEM source (like mine) to:

[Tasks]
Remove Components
Unattended Setup
Integrate Drivers
Tweaks
Create a Bootable ISO
Options

The language is kind of irrelevant. I've already checked with a "translator" to compare. The "run" was done with Spanish as the Language against a Dell Spanish source (apparently based on the OP's comments and the INI).

Edited by submix8c
0

Share this post


Link to post
Share on other sites

To sum it up, it's all resulting in a cosmetic problem that is triggered by a deliberate unneeded change and that has no consequence at all since the resulting install is for personal use only. Well, not a big deal I would say.

0

Share this post


Link to post
Share on other sites

Basics of the sysoc file:

It is used mainly during windows setup to tell windows which .inf's to run to install windows components.

The ones with the "Hide" in the entry have those FOR a reason!

Mainly due to the fact the entries are NOT entered to make that component removable!

Or

Removing it can usually cause instabilties or damage.

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.