• 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.
bensam56

RT Seven Lite - RC build 1.7.0 and Beta build 2.6.0

1,970 posts in this topic

Thanks Grabben. So what you are saying is that I can load updates for both x86 and x64 - all in the same window? And then to finalize, do I need to Build Current Image, Re-Build All, or Optimize Boot and Wim?*editI just tried to combine updates for both OS's, and it doesn't appear like it can be done. After adding in all the updates for x86, I then try to add the ones for x64. It gives me an error that says "This Package is already in queue". Apparently it is unable to add the same KB article numbers for the different OS architecture's. There are only two that do not have the same article number and those show in red (probably because I chose 7 Ultimate x86 when I started).Any thoughts?
Not in the same window or on to all edtions at once, you will have to do each edition, one at time..

But that sure would be something :P

Edited by grabben
0

Share this post


Link to post
Share on other sites

Is there a change between 1.06 and 1.07 that could relate to the fact that suddenly makes it impossible to run UPEK Protector Suite 2009 (with the legacy drivers, not the Windows Biometrics drivers)?

In addition to what I removed from the 1.06 install, I removed this in the not-working v1.07 stripped install:

IIS-WebServerRole=True

TelnetClient=True

TelnetServer=True

SensrSvc=True

sppuinotify=True

Manual windows setup=True

Recovery=True

Any of the applications, save the tray icon UI, simply crashes whenever I try to start it:

Event ID 1000

The following information was included with the event:

ctlcntrv.exe

5.9.3.6241

4bb09897

KERNELBASE.dll

6.1.7600.16385

4a5bdfe0

e0434f4d

000000000000aa7d

Process Monitor:

1788	QueryOpen	C:\Windows\System32\MSCOREE.DLL.local	NAME NOT FOUND
1788 QueryOpen C:\Program Files\Protector Suite\ctlcntrv.exe.Local NAME NOT FOUND
1788 QueryOpen C:\Windows\Microsoft.NET\Framework64\v2.0.50727\fusion.localgac NAME NOT FOUND
1788 CreateFile C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\security.config NAME NOT FOUND
1788 CreateFile C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\security.config.cch NAME NOT FOUND
1788 CreateFile C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\enterprisesec.config NAME NOT FOUND
1788 CreateFile C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\enterprisesec.config.cch NAME NOT FOUND
1788 QueryOpen C:\Program Files\Protector Suite\profapi.dll NAME NOT FOUND
1788 CreateFile C:\Users\Guillaume\AppData\Roaming\Microsoft\CLR Security Config\v2.0.50727.312\64bit\security.config PATH NOT FOUND
1788 CreateFile C:\Users\Guillaume\AppData\Roaming\Microsoft\CLR Security Config\v2.0.50727.312\64bit\security.config.cch PATH NOT FOUND
1788 QueryDirectory C:\Windows\assembly\GAC_64\mscorlib\2.0.0.0__b77a5c561934e089\mscorlib.INI NO SUCH FILE
1788 QueryOpen C:\Windows\Microsoft.NET\Framework64\v2.0.50727\ole32.dll NAME NOT FOUND
1788 QueryOpen C:\Program Files\Protector Suite\CRYPTBASE.dll NAME NOT FOUND
1788 QueryDirectory C:\Program Files\Protector Suite\ctlcntrv.INI NO SUCH FILE
1788 QueryOpen C:\Windows\assembly\GAC\PublisherPolicy.tme NAME NOT FOUND
1788 QueryOpen C:\Windows\assembly\NativeImages_v2.0.50727_64\WindowsBase\385daef1d59c01201d35cdd277f99a56\WindowsBase.ni.dll PATH NOT FOUND
1788 QueryOpen C:\Windows\assembly\GAC_64\PresentationFramework\3.0.0.0__31bf3856ad364e35 PATH NOT FOUND
1788 QueryOpen C:\Windows\assembly\GAC_MSIL\PresentationFramework\3.0.0.0__31bf3856ad364e35 PATH NOT FOUND
1788 QueryOpen C:\Windows\assembly\GAC\PresentationFramework\3.0.0.0__31bf3856ad364e35 PATH NOT FOUND
1788 QueryOpen C:\Program Files\Protector Suite\PresentationFramework.dll NAME NOT FOUND
1788 QueryOpen C:\Program Files\Protector Suite\PresentationFramework\PresentationFramework.dll PATH NOT FOUND
1788 QueryOpen C:\Program Files\Protector Suite\PresentationFramework.exe NAME NOT FOUND
1788 QueryOpen C:\Program Files\Protector Suite\PresentationFramework\PresentationFramework.exe PATH NOT FOUND
1788 QueryOpen C:\Program Files\Protector Suite\ctlcntrv.exe.Local NAME NOT FOUND
1788 QueryOpen C:\Windows\Microsoft.NET\Framework64\v2.0.50727\en-US\mscorrc.dll PATH NOT FOUND
1788 QueryOpen C:\Windows\Microsoft.NET\Framework64\v2.0.50727\en-US\mscorrc.dll.DLL PATH NOT FOUND
1788 QueryOpen C:\Windows\Microsoft.NET\Framework64\v2.0.50727\en\mscorrc.dll PATH NOT FOUND
1788 QueryOpen C:\Windows\Microsoft.NET\Framework64\v2.0.50727\en\mscorrc.dll.DLL PATH NOT FOUND
1788 QueryOpen C:\Windows\Globalization\en-us.nlp NAME NOT FOUND
1788 QueryOpen C:\Windows\Microsoft.NET\Framework64\v2.0.50727\VERSION.dll NAME NOT FOUND
1788 QueryOpen C:\Program Files\Protector Suite\VERSION.dll NAME NOT FOUND

Edited by Guillaume
0

Share this post


Link to post
Share on other sites

Is there a change between 1.06 and 1.07 that could relate to the fact that suddenly makes it impossible to run UPEK Protector Suite 2009 (with the legacy drivers, not the Windows Biometrics drivers)?

It looks like you are missing chunks of .NET, which may be a prerequisite for your application. Tell me, did you tick "winsxs cache" for removal? I've had a similar issue with the latest beta, and Ben indicates this should be resolved in the near future. If you absolutely can't wait for the next release, you can try to untick the winsxs cache removal option and rebuild your .iso with the same options.

0

Share this post


Link to post
Share on other sites

Seems like it's got everything to do with the absence of folders in C:\Windows\assembly: it searches for all kinds of non-existing folders like C:\Windows\assembly\GAC_64\PresentationFramework\3.0.0.0__31bf3856ad364e35. If I create them and symlink to C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\v3.0\ the program gets started a little bit further each time, but I can't get it to work completely.

Does RT7Lite mingle with the Windows\assembly folder?

Edit

Copying the entire \Windows\assembly folder from a fresh image fixed the problem.

Edited by Guillaume
0

Share this post


Link to post
Share on other sites
Thanks Grabben. So what you are saying is that I can load updates for both x86 and x64 - all in the same window? And then to finalize, do I need to Build Current Image, Re-Build All, or Optimize Boot and Wim?*editI just tried to combine updates for both OS's, and it doesn't appear like it can be done. After adding in all the updates for x86, I then try to add the ones for x64. It gives me an error that says "This Package is already in queue". Apparently it is unable to add the same KB article numbers for the different OS architecture's. There are only two that do not have the same article number and those show in red (probably because I chose 7 Ultimate x86 when I started).Any thoughts?
Not in the same window or on to all edtions at once, you will have to do each edition, one at time..

But that sure would be something :P

So, after running rt lite on each edition (that's going to take forever), should I use the Build Current Image, Re-Build All, or Optimize Boot and Wim?

I just thought of something too. What if I were to take an untouched iso, one x64 and one x86, and change them using rt lite. Then export the install.wim of each edition that I want combined into one and then replace the install.wim in the x86 sources folder?

0

Share this post


Link to post
Share on other sites

Copying the entire \Windows\assembly folder from a fresh image fixed the problem.

I'd still be interested in knowing whether or not you chose the option to remove the winsxs cache. That option borks .Net; I wouldn't be surprised if it also wrecked \assembly.

0

Share this post


Link to post
Share on other sites
Thanks Grabben. So what you are saying is that I can load updates for both x86 and x64 - all in the same window? And then to finalize, do I need to Build Current Image, Re-Build All, or Optimize Boot and Wim?*editI just tried to combine updates for both OS's, and it doesn't appear like it can be done. After adding in all the updates for x86, I then try to add the ones for x64. It gives me an error that says "This Package is already in queue". Apparently it is unable to add the same KB article numbers for the different OS architecture's. There are only two that do not have the same article number and those show in red (probably because I chose 7 Ultimate x86 when I started).Any thoughts?
Not in the same window or on to all edtions at once, you will have to do each edition, one at time..

But that sure would be something :P

So, after running rt lite on each edition (that's going to take forever), should I use the Build Current Image, Re-Build All, or Optimize Boot and Wim?

I just thought of something too. What if I were to take an untouched iso, one x64 and one x86, and change them using rt lite. Then export the install.wim of each edition that I want combined into one and then replace the install.wim in the x86 sources folder?

Not sure but if its equivalent to vLite its "re-build all"

Ofcourse you can first modify the 32bit and 64bit seperately and then export them to a new .wim. Thats the basic idea of creating an AIO.

0

Share this post


Link to post
Share on other sites

Copying the entire \Windows\assembly folder from a fresh image fixed the problem.

I'd still be interested in knowing whether or not you chose the option to remove the winsxs cache. That option borks .Net; I wouldn't be surprised if it also wrecked \assembly.

Yeah I did. It was all about the .NET in this case, yeah (UPEK Protector Suite uses .NET 3.0)

I was thinking, though: the files that are removed are (primarily at least) files that are normally duplicates present in another folder. So wouldn't it be a great idea to not just remove the duplicates (which obviously breaks stuff), but to substitute them for symbolic links? That'll save the same disk space, but keep the .NET support in tact.

0

Share this post


Link to post
Share on other sites

I was thinking, though: the files that are removed are (primarily at least) files that are normally duplicates present in another folder. So wouldn't it be a great idea to not just remove the duplicates (which obviously breaks stuff), but to substitute them for symbolic links? That'll save the same disk space, but keep the .NET support in tact.

It sounds like you have more of a handle on it than I do, but the issue was present in an pre-beta 1.08 and Ben said that he could fix it. He seems to me a man of his word. :)

0

Share this post


Link to post
Share on other sites

I was thinking, though: the files that are removed are (primarily at least) files that are normally duplicates present in another folder. So wouldn't it be a great idea to not just remove the duplicates (which obviously breaks stuff), but to substitute them for symbolic links? That'll save the same disk space, but keep the .NET support in tact.

It sounds like you have more of a handle on it than I do, but the issue was present in an pre-beta 1.08 and Ben said that he could fix it. He seems to me a man of his word. :)

Well, yeah, I started out doing the symbolic linking myself and it worked out pretty nicely, but since I don't exactly have a list of what is removed it's a bit more work for me than it is for Ben, who knows in advance what is 'missing'. In essence, I think symbolic linking would be an absolute brilliant solution.

0

Share this post


Link to post
Share on other sites

Is there a chance this "fix" for the Documents and Settings rights issue is going to be released this month so people who are currently stuck with that can give it a shot too?

0

Share this post


Link to post
Share on other sites

The settings that I'm using on rt seven lite are messing up with my windows live messenger.

I've tested it in different PCs, with different internet networks and software (and no AV/Firewall) and my MSN cant login.

Using this settings on 1.0.7 (In attachment).

Can you please check what I shouldn't remove so I can use MSN?

0

Share this post


Link to post
Share on other sites

I use Amsn without any problem. You can try it like alternative.

0

Share this post


Link to post
Share on other sites

I use Amsn without any problem. You can try it like alternative.

Just wondering witch component I removed is messing around my MSN!

0

Share this post


Link to post
Share on other sites

Have you disabled or removed some services?

0

Share this post


Link to post
Share on other sites

Have you disabled or removed some services?

I only used the Features Removal tab.

Services I removed:

BitLocker Drive Encryption Service

Disk Defragmenter

Offline Files

Parental Controls

Problem Reports and Solutions Control Panel Support

Program Compatibility Assistant Service

Protected Storage

Remove Access Auto Connection Manager

Remove Access Connection Manager

Remote Desktop Configuration

Remote Desktop Services

Remote Desktop Services UserMode Port Redirector

Remote Registry

Windows Backup

Windows Biometric Service

Windows Card Space

Windows Defender

Windows Error Reporting

0

Share this post


Link to post
Share on other sites

Why do you have removed the service instead disable? I don't remove nothing but only disable. If you disable it can be re-enable but once removed you cannot re-enable. I'm sorry but o don't use a original Messenger but you can repeat the tweak , trying ti disable instead remove. I think that is a good way to resolve or atleast to try.

0

Share this post


Link to post
Share on other sites

Services I removed:

BitLocker Drive Encryption Service

Disk Defragmenter

Offline Files

Parental Controls

Problem Reports and Solutions Control Panel Support

Program Compatibility Assistant Service

Protected Storage

Remove Access Auto Connection Manager

Remove Access Connection Manager

Remote Desktop Configuration

Remote Desktop Services

Remote Desktop Services UserMode Port Redirector

Remote Registry

Windows Backup

Windows Biometric Service

Windows Card Space

Windows Defender

Windows Error Reporting

Live Messenger is working for me.

The ones with Green i have disabled or they run manually.Im pretty sure these are not needed for WLM

The Orange one could cause problems for WLM if its removed

The Red ones i have enabled always

0

Share this post


Link to post
Share on other sites

Services I removed:

BitLocker Drive Encryption Service

Disk Defragmenter

Offline Files

Parental Controls

Problem Reports and Solutions Control Panel Support

Program Compatibility Assistant Service

Protected Storage

Remove Access Auto Connection Manager

Remove Access Connection Manager

Remote Desktop Configuration

Remote Desktop Services

Remote Desktop Services UserMode Port Redirector

Remote Registry

Windows Backup

Windows Biometric Service

Windows Card Space

Windows Defender

Windows Error Reporting

Live Messenger is working for me.

The ones with Green i have disabled or they run manually.Im pretty sure these are not needed for WLM

The Orange one could cause problems for WLM if its removed

The Red ones i have enabled always

Error Reporting is useless, but removing Remote Access Auto Connection Manager and/or Remote Access Connection Manager is a b*tch. So I recommend you don't remove those two. Additionally, I don't know if it's that good of an idea to remove Protected Storage.

Edited by Guillaume
0

Share this post


Link to post
Share on other sites
Additionally, I don't know if it's that good of an idea to remove Protected Storage.

If you remove Protected Storage, software will not remember your passwords. So security-wise, it's a good idea to remove.

0

Share this post


Link to post
Share on other sites
Additionally, I don't know if it's that good of an idea to remove Protected Storage.

If you remove Protected Storage, software will not remember your passwords. So security-wise, it's a good idea to remove.

All passwords? Like in Opera passwords also? So button "Remember password" will be useless?

0

Share this post


Link to post
Share on other sites

All passwords? Like in Opera passwords also? So button "Remember password" will be useless?

Correct.

Edited by BladedThesis
0

Share this post


Link to post
Share on other sites

I'm going to make my first win7 x64 customization CD and I want to ask you guys if things I want to remove are safe to remove and maybe you have some ideas what else is safe to remove and completely useless.

* This is based on 32-bit ISO image but this week I will received 64-bit operating system. I think the main difference will be that x64 version will have some more services? Ok, here is it:

Pernamently remove:

Accessories --------------

On-Screen Magnifier

Welcome Center

Windows Repair Disc

Drivers ------------------

Intel Corporation

NVIDIA

Creative Technology

TV Tuners

Language Packs ------------

All

Multi-Media ---------------

Sample Music and Videos

Sample Pictures

Screensavers

Network -------------------

Telnet Client

Telnet Server

Services ------------------

BitLocker Drive Encryption Service

Parental Controls

Problem Reports and Solutions Control Panel Support

Program Compatibility Assistant Service (can I remove a program, not only a service?)

Remote Registry

Smart Card Removal Policy

Windows Backup

Windows Error Reporting Service

Windows Card Space

Windows Biometric Service

System --------------------

Recovery

Tablet PC

Windows Anytime Upgrade

Default features:

Tablet PC Components

Telnet Client

Telnet Server

I'm a regular user. I don't work with any servers or networks. Just connecting to wifi router and browsing internet. Most of time working on MS Word, playing some games from time to time. What do you think I can safely remove then?

Edited by michal_banszel
0

Share this post


Link to post
Share on other sites

Nobody can help? Mostly I'm wondering if it's safe to remove telnet stuff... ?

Edited by michal_banszel
0

Share this post


Link to post
Share on other sites

Maybe no one will respond because you know just what you need or not. . Telnet is NOT a basic function for the operating system. Its removal should not create any problem. Remove the server will prevent that we can connect to your PC using this protocol (improve security) . If you also remove the client, you can not connect to any machine that has a telnet server running.

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

  • Recently Browsing   0 members

    No registered users viewing this page.