Page 3 of 3
Re: noscript update wonky, need previous version
Posted: Fri May 04, 2012 5:04 am
by GµårÐïåñ
If only my manufacturer would look that good supporting me, I would be a happier hacker
Re: noscript update wonky, need previous version
Posted: Fri May 04, 2012 5:09 am
by Tom T.
GµårÐïåñ wrote:If only my manufacturer would look that good supporting me, I would be a happier hacker
Surely an advanced hacker like yourself knows how to put whatever image is desired in that box, in place of a dull OEM logo ...
Re: noscript update wonky, need previous version
Posted: Fri May 04, 2012 6:40 am
by GµårÐïåñ
Of course silly, I was just having a little fun...pre-vista you put it in the system32 folder now you have to do it in the registry but the basic files are all the same. ish.
Re: noscript update wonky, need previous version
Posted: Fri May 04, 2012 7:42 am
by Tom T.
GµårÐïåñ wrote:Of course silly, I was just having a little fun...pre-vista you put it in the system32 folder now you have to do it in the registry but the basic files are all the same. ish.
Another "regression" in Vista.
-- no messing with the registry to change OEM logo in XP.
Re: noscript update wonky, need previous version
Posted: Fri May 04, 2012 8:36 pm
by GµårÐïåñ
Correct, the OEM info was in an ini/inf file before now the logo files are in the the same place but the information is coded in the registry, as part of the pre-coding by manufacturers, loading a registry payload was deemed easier for branding purposes, personally I always wipe and clean install any machine I get anyway, so never been an issue for me. If I am doing it for people, I put the support information needed for them to get a hold of ME for help, but that's about it. I have a slip script for both, so it takes seconds but yeah arguments can be made for/against both methods.
Re: noscript update wonky, need previous version
Posted: Sat May 05, 2012 2:12 am
by Tom T.
GµårÐïåñ wrote:the OEM info was in an ini/inf file before now the logo files are in the the same place but the information is coded in the registry...
The info and support info, yes, but the logo was simply a system32 file called oemlogo.bmp -- for which any .bmp can be substituted.
GµårÐïåñ wrote:... loading a registry payload was deemed easier for branding purposes...arguments can be made for/against both methods.
I think you mean, "harder for users to remove the brand logo".
I don't see any argument "for", except for the one above.
Re: noscript update wonky, need previous version
Posted: Tue May 08, 2012 6:41 am
by GµårÐïåñ
That's what I said, the file is still there, the information is in the registry instead of the setup file. And I meant easier for the vendors not the users.
Re: noscript update wonky, need previous version
Posted: Tue May 08, 2012 8:57 am
by Tom T.
GµårÐïåñ wrote:.... And I meant easier for the vendors not the users.
LOL Gotcha.
