bensam56

Use it for your personal not workstation PC's or lap

Seemed like absolutely nothing happened.. just a slightly misplaced arrow spinning around at unattended. Didnt freeze or mess up the computer, nothing happened for a long time. First when i choosed to exit the program, it gave me the .NET Framework error and then it was cleaning temporary blabla, also that took some time. Once you got some exception error....app will stop the remaining process.....ofcourse cleaning temp files needs some 1 min....to clean your mounted image. Anyhow next version will be released by tomorrow... Thumbs up Any changelog ? I added some new features and fixed most of the things....I know all my previous versions removed some important files and tweaks not applied properly. I will put the changes in main site and here by tomorrow

Seemed like absolutely nothing happened.. just a slightly misplaced arrow spinning around at unattended. Didnt freeze or mess up the computer, nothing happened for a long time. First when i choosed to exit the program, it gave me the .NET Framework error and then it was cleaning temporary blabla, also that took some time. Once you got some exception error....app will stop the remaining process.....ofcourse cleaning temp files needs some 1 min....to clean your mounted image. Anyhow next version will be released by tomorrow...

I will get this to my mind....and will apply it in final.

Oh yes, I fixed that. No need to disable UAC hereafter

I'm sure those issues will be solved in next build. But I cannot give assure for XP hosts

I'm trying to finish ASAP...i fixed almost what i got in feedback. I added some new features also...I'm going to send this build to 3 beta testers here in MSFN before it reaches the public.

its based on dism. So as per Microsoft said I mentioned up ther. Removing components and other tweaks process can be done under XP. Next build i'm not gonna use dism.

yes...this is a small bug. I missed to add that for deletion. Thank you. It will be fixed

These errors will be fixed in next build which will be available within this week

I used vlite to mount win 7 and closed the app in the middle, samething happened and tried to unmount using dism says image is corrupted. Also tried imagex but no luck same error...So this corrupted mounted image wont be saved to WIM. So I deleted the mounted folder and its deleted. The problem is not on *S-1-5-32-544 or on language....

Thank you Mr. Nitro

which version you are using?

next week....on or before Wednesday

Thank you for reporting my friend...i will fix this

dism /unmount-wim /mountdir:%temp%\RT_Mount /discard dism /cleanup-wim (to clean all mounted images)

make sure whether you already mounted that same wim using any other apps and missed to unmount.....!

are you running from the built in admin account? that is the exact same error i got when i did that. you can not run rt7lite from within the built in admin account. you need to create a user account with admin privileges. MMMMM, yeah I was running from a built admin account - eh, on a Windows 7 Enterprise 64-bit O/S. Alright, I'll give that a shot and see how that goes...thanks hclarkjr. did that fix it for you? hopefully ben can find way for it to be run from the built in admin account Unfortunately, no, I tried run from non - built in admin account and still get back the same error - see the attach pic below - I'm thinking there is a conflict with Windows 7 Enterprise 64Bit and the RT 7 Lite...I don't know, I can only guess. MMMMM Whats your current host OS language?

Did you got the default features list in the right side?

Isn't that backwards? syswow64 represents the 32 bit stuff "The operating system uses the %SystemRoot%\system32 directory for its 64-bit library and executable files. This is done for backwards compatibility reasons as many legacy applications are hardcoded to use that path. When executing 32-bit applications, WOW64 redirects requests for DLLs from that directory to %SystemRoot%\sysWOW64, which contains legacy libraries and executables." Not backwards...our app is compiled for x86 architecture only not all....so it will look for syswow64

I will make a video tutorial for this. I removed the list of components which I listed out...it removed 1 GB out of 2.5 GB source

You selected <SkipMachineOOBE>true</SkipMachineOOBE> make it as "False" select this option only if you enabled skip user creation and using adminstrator account

I will bring build 1.05 a stable one.....where some of the important system cannot be deleted. Thank you "Tomorrow" for checking by deleting some of the important applications and reporting me. * I will also make an automatic updates receiver for rt 7 lite. So that you will get the updates directly on your computer and it will download the installer.

which file you tried to add in secure list? I had the same problem but i figured it out.There is no need to include path for the protected file like windows\system32\Magnification.dll Simply add Magnification.dll and thats it. I added these: *What does this Red/Purple mean when i added a driver?.It will not be integrated?: *Also maybe it just seems to me but 7 Lite seems very unstable when i add bunch of drivers.Always collapses with unhandeled exeption Ill try adding from shorter path or drive root, maybe 7 Lite doesent like my long folder names. *What to think of this error?.Happened during Integration(Hotfixes i think).I clicked Ok and 7 Lite seemed to continue just fine. *Also 7 Lite seems unable to resume from minimize.After it starts integrations etc i choose minimize but i am unable to bring it back to foreground until it has finished current operations. Red color will appear if the architecture is different from the mounted image. In next build i will set the priority level. Which hotfix is that? Can you tell me the KB number?

which file you tried to add in secure list?