Jump to content

Clint

Member
  • Posts

    426
  • Joined

  • Last visited

  • Donations

    $0.00 

Everything posted by Clint

  1. No, still not true. It is percentage based (sorta), if you have less memory available it will take less..(all within a certain range). Read up on it.. And have you understand what the Readyboost feature is? It will pull/give nothing until it's activated, and for that you will need an External Memory Device...like USB drive, SD Card, Compact Flash, or other flash memory device that is connected to your computer. It does absolutely nothing on it's own...so if it's removed it will save/gain nothing in memoryusage. ..don't "recommend" this and that if you don't know the facts...
  2. Not really. Vista's memorymanagement work in a different way than in XP. It will pull 30-33% of available memory until a certain point. If you have only 512mb in the machine and some other gadgets running it will be happy to pull only 190-200mb for the core alone and perhaps 30-40mb for AV and such. This is how MS make "their new OS" more snappy than XP..(it's still the same s*** except memory and prefetch management). Fact.
  3. Thanks for the answer, good to know I'm not alone with that error. I will investigate further. Thanks!
  4. I'm trying to get a grip on how to edit the boot.wim properly. I use these commands: imagex /mountrw C:\Vista\sources\boot.wim 2 C:\Mount.PE imagex /unmount /commit C:\Mount.PE ImageX /export /check /compress maximum C:\Vista\sources\boot.wim 2 C:\newboot.wim I get an extracted image #2 message.. ..but after renaming the wim and replace the original boot.wim I get this error when trying to install: Is it a different approach to edit this image? thanks!
  5. Well, I started the thread...and I never discussed vLite...(only certain ppl's behaviour perhaps) My last post was about how to remove components properly, and that has nothing to do with vLite....only Microsoft...and us here
  6. Very true, but Vista is actually much much easier to modify. ..childsplay really, you can mount the Vistas registry in XP or whatever and then do your changes...unload it and then commit. Too easy As for components you simply edit a .xml file that gets parsed...get rid/edit Manifests and related componentpackages and files...and your done! ...but who am I to come here and pretend I know this...when we have all these clever nlite/vlite buttonclickers that seems to know sooooo much more.
  7. Actually I found that in the Doc a few days ago, but I forgot what this thread was about in the first place due to all the moronic attitudes... Anyway, I've been localizing most of the needed info now for my work on this. I don't know how far you have come when it comes to editing the registry in the image and removing components, but I have got it pretty much laid out now. I have got all the services and components mapped out and sorted. It's all about just a few locations if you want to do it right. Thanks for helping out!
  8. Maybe you could give an explanation on why I should visit a doctor?
  9. Yeye, avoid it and ignore all requests even for a simple regtweak...very good for community. ..and I'm not bitter...and not near a "copycat" of you...actually ahead of you dude.
  10. Yeyeye, same answer as I was expecting...and you are simply lying when you say you allways answer on tweak-specific questions....that are related to Microsoft Windows OS...NOT nlite or vlite....I have NEVER seen you answer any of those questions..(and they are quite a few). You know, here do we share tweaks and such that are related to Windows...thats the core mentality of this board....so don't come dragging with "bust my a**"....and you saying that you never pull info here...that is almost an insult to your fellow members. ..and that talk about "copycat" and "show me another nlite or vlite" is just giving yourself away my friend..big headed and bloated mind from all those 'nlite button clickers' fanboys around you is what I say.
  11. Hehe, I'm not bitter...have no reason to be Just complaining that you never give out any info or hints regarding tweaks, registry edits or similar...only pulling info...and I'm not talking about specific nlite/vlite code. But then you might wanna break the trend and give a hint on where you disable OOBE then?
  12. Ask Nuhi where he has hidden the Unattended that is created with Vlite, or he has done a sxs package or similar...maybe in the system or components hive as well. I seriously doubt he will answer though...
  13. Yes, a verified working basic config sample would be benefitial to a lot of newbies like me. Thanks fellas! ..the weird part is that I get my AutoUnattend passed in WAIK but it still hangs at the end of install.. ..and it changes the resolution in the beginning of install so it obviously passes the entries before that...very odd.
  14. This is killing me! Here is my code: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> </component> <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ComplianceCheck> <DisplayReport>Never</DisplayReport> </ComplianceCheck> <UserData> <ProductKey> <WillShowUI>OnError</WillShowUI> </ProductKey> </UserData> <Display> <ColorDepth>32</ColorDepth> <HorizontalResolution>1024</HorizontalResolution> <VerticalResolution>768</VerticalResolution> </Display> <UseConfigurationSet>true</UseConfigurationSet> <DiskConfiguration> <WillShowUI>Always</WillShowUI> </DiskConfiguration> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <OEMInformation> <Manufacturer>The TEAM</Manufacturer> <Model>VISTA Gamers Ed.</Model> </OEMInformation> <OOBE> <HideEULAPage>true</HideEULAPage> <NetworkLocation>Other</NetworkLocation> <ProtectYourPC>3</ProtectYourPC> <SkipUserOOBE>true</SkipUserOOBE> </OOBE> <Display> <ColorDepth>32</ColorDepth> <HorizontalResolution>1024</HorizontalResolution> <VerticalResolution>768</VerticalResolution> </Display> <VisualEffects> <FontSmoothing>ClearType</FontSmoothing> </VisualEffects> <TimeZone>Central Standard Time</TimeZone> </component> </settings> <cpi:offlineImage cpi:source="wim:c:/vista/sources/install.wim#Windows Vista ULTIMATE" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend> I still get that darn "minimum 512mb" popup..! Please guide me here... Thanks!
  15. EDIT: I can't get this to work...! Are you sure it should be a "windowsPE" title and then component name "Microsoft-Windows-Setup" ? Thanks!
  16. I must ventilate this: After upgrade the UI is a bit different, I can live with that. A bit annoying is the fact that the emoticons aren't sorted after most commonly used, the first set of emoticons should ofcourse be the most commonly ones used. As it is now you'll have to click next everytime to get a regular smiley, not very well thought out. Also when using the smiley option now, the code will stay highlighted...meaning I must hit space or arrow before typing on...otherwise I will write over it....again not very well thought out. ...upgrades are supposed to improve things.
  17. Thanks for helping out! How does this loke like? I can't understand why the "offlineImage" line has to be there, can't I just remove it? <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> </component> <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <UserData> <ProductKey> <WillShowUI>OnError</WillShowUI> </ProductKey> </UserData> <Display> <ColorDepth>32</ColorDepth> <HorizontalResolution>1024</HorizontalResolution> <VerticalResolution>768</VerticalResolution> </Display> <UseConfigurationSet>true</UseConfigurationSet> <DiskConfiguration> <WillShowUI>Always</WillShowUI> </DiskConfiguration> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <OEMInformation> <Manufacturer>The TEAM</Manufacturer> <Model>VISTA Gamers Ed.</Model> </OEMInformation> <OOBE> <HideEULAPage>true</HideEULAPage> <NetworkLocation>Other</NetworkLocation> <ProtectYourPC>3</ProtectYourPC> <SkipMachineOOBE>true</SkipMachineOOBE> <SkipUserOOBE>true</SkipUserOOBE> </OOBE> <Display> <ColorDepth>32</ColorDepth> <HorizontalResolution>1024</HorizontalResolution> <VerticalResolution>768</VerticalResolution> </Display> <VisualEffects> <FontSmoothing>ClearType</FontSmoothing> </VisualEffects> <TimeZone>Central Standard Time</TimeZone> </component> </settings> <cpi:offlineImage cpi:source="wim:c:/vista/sources/install.wim#Windows Vista ULTIMATE" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend> ..it will still give me errors at install with this EDIT: Is it just me, or hasn't the board gotten changed to the worse...the user UI is terrible.
  18. **** this AutoUnattend.xml crap! I get errors and whatnot all the time, and the helpfiles are not of much help when it comes to understand the format. I only need to have this settings applied, nothing more: <OOBE> <HideEULAPage>true</HideEULAPage> <NetworkLocation>Other</NetworkLocation> <ProtectYourPC>3</ProtectYourPC> <SkipMachineOOBE>true</SkipMachineOOBE> <SkipUserOOBE>true</SkipUserOOBE> </OOBE> ..I only need a template to use for this only, coz I do constant installs in VMware and this will save me 3min each time. Can someone give me a little bit of code? Thanks!
  19. Actually I was aiming at the check at first boot that will stop you from installing if you don't meet the minimum requirements. I've started to pull this thing apart and from the looks of it will 256mb of memory do just fine, so I need to remove that check that will popup and demand 512mb system memory.
  20. Hi again boys! I need to disable that "minimum system requirements" check in the beginning of install. It should be possible to change the value or disable it somewhere.. Thanks!
  21. Problem solved! As you said must I use the same switch as in the original image, so when I apply "/compress fast" it works. One could think it would work without switch when fast is default...but this is how things are.. Thanks for the help!
  22. No, that seems only to be a higher compression...it takes a much longer time to compress with that switch. Are you meaning this will force the changes to the image as well? EDIT: After testing I can't see any changes in size from removal of files using that switch. Can someone please give me a hint on this, this is getting very annoying...
  23. Ok, this is getting silly... I first mount the image with: imagex /mountrw C:\Vista\sources\install.wim 4 C:\Mount.VISTA I then remove files and stuff from the mounted image worth something like 300mb. I then unmount it with: imagex /unmount /commit C:\Mount.VISTA After that I copy the image: ImageX /export /check C:\Vista\sources\install.wim 4 C:\newinstall.wim ...but the newinstall.wim is STILL the same size as the original install.wim...??? wtf?!? this can't be this complicated..


×
×
  • Create New...