FarCry3r
Content Type
Profiles
Forums
Events
Posts posted by FarCry3r
-
-
I was referring to the wrong person. LOL! Sorry. Anyway, never ever burn the ISO unless you're satisfied with the result...
0 -
There is no need to make the ISO if you are not going to use a CD. Read the sticky posts in the sub forum called "Install XP from USB", download "USB_Multiboot_10" and run it. If you removed the "manual install" (winnt.exe) in your nLite process, you will have to start over again.
There's a need to create ISO even though you didn't use a CD, that is for testing the modified installer source. It's always faster booting in virtual machine using an ISO file than from USB (if it's supported). Plus if I remembered correctly, there's no need for "manual install" to be included since you're booting from USB, thus no GUI is needed.
0 -
Does anyone know how to make vLite work with Windows 7? The installer didn't even load, just throwing out bunch of UI error...
0 -
it's pre-beta, what do you expect?
pre-beta is just an insight of what is to come, ms don't release them publicly to the masses for a reason
this will shape out very nicely, just wait for the rtm
And this 6801 build is for developers only...
0 -
I remove a hell of a lot of components using vlite (i only keep about 5-6 things with extreme, paint, notepad, .NET and a few others) with the current installation of Windows 7 6801... it runs at the same performance of my vista vlited install with is great! Did i forget to mention that it is a non-vlited install of Windows 7
so what's was that? Or i read it wrong?
I remove a lot of components with windows vista...... Windows 7 (full) runs faster than my fully vlited vista install.
Sorry then, I thought you did it on 6801
0 -
Now, how do you got vLite working with 6801? I can't get it work, during setup, it says cannot open install.wim... wtf
Legolash2go did mention it does not work with build 6801..
vLite did work with Windows 7 but not the latest 6801 release.but then he said:
I remove a hell of a lot of components using vlite (i only keep about 5-6 things with extreme, paint, notepad, .NET and a few others) with the current installation of Windows 7 6801... it runs at the same performance of my vista vlited install with is great! Did i forget to mention that it is a non-vlited install of Windows 7so what's was that? Or i read it wrong?
0 -
it does exist, not legally that is...
Sure it does. Who are you to say that anyone here is not an MS employee or an authorized OEM?
And who are you to question what I typed?
Someone who might legally have it.
So what's the point of your question? I know some might have it legally, but the rest are not.
0 -
it does exist, not legally that is...
Sure it does. Who are you to say that anyone here is not an MS employee or an authorized OEM?
And who are you to question what I typed?
0 -
vLite did work with Windows 7 but not the latest 6801 release.
I remove a hell of a lot of components using vlite (i only keep about 5-6 things with extreme, paint, notepad, .NET and a few others) with the current installation of Windows 7 6801... it runs at the same performance of my vista vlited install with is great! Did i forget to mention that it is a non-vlited install of Windows 7
boot time, install time, app launch times, so on?Boot Time: 4 out of 5 (no need to count... nice boot screen though)
Install Time:5/5 - 23 mins
App Launch Times: 4.5/5 Very quick (even when i never opened the app before) Minefield opens up instantly.
CPU: between 1% and 9% (Intel Pentium Dual-Core T2370 2x 1.73Ghz)
Memory Uage: 45% (2GB RAM DDR2) with Office 2007 installing and MSN, Minefield (Firefox Alpha) running..
User Interface: Love it! Much Much smoother, nice visual effects, etc...
Sound: Crackles a lot (for me anyway, the logon sound... sounded horrible) - built-in sound card on laptop
Wallpapers: Better than XP
Themes: pretty much the same but got more choice.
Drivers: Uses Vista Drivers
Windows Update UI looks nice
New WMP takes a while to get used to
Bugs
Start Menu sometimes does not open
Again, sound crackles but not really a bug i dont think
Now, how do you got vLite working with 6801? I can't get it work, during setup, it says cannot open install.wim... wtf
0 -
The first card I got was a Riva TNT2 which while it wasn't particularly fast (when I got it) still played games for almost 2 years before I switched to ATI and got the 9600 Pro and then (a good bit later) the X850 XT PE. While I upgraded twice, a friend of mine got a Ti4400 (or was it 4600?) and it lasted him for 4 years and he was even able to play GTA San Andreas on it (although not very nicely).
I've always found Nvidia's cards last fairly long, and they have nice features, while ATI cards (ignoring the 2xxx series) were always pretty good on power and performance but somehow had to be replaced after a while. If Nvidia got their act together now and managed to fix their drivers for the 9xxx and 2xx series then they should be able to edge up to ATI.
I'm definitely interested in seeing the next line of cards from both manufacturers.
I still have my good old SAPPHIRE ATi 9550 card and playing C&C3 and Crysis with it, although not very nice to play, ATi are the best, forget nVIDIA with their lies, problems, etc. ATi to the end!
0 -
it does exist, not legally that is...
0 -
no solution anyone?
0 -
since it's my own custom distribution (and vLited), you won't see anything different with any other vLited output
I'm not following, can you or can you not use vLite?
Is this an issue of vLiting a previously vLited installation? Have you tried starting fresh, wtihout any tampering from the original DVD?
Yes, this is an issue of vLiting a previously vLited source which I vLited myself not Dell or other ppl. Before this, I can integrate any hotfixes (post SP1) without problem even if I already vLited it dozens of time, but not recently with that I-don't-know-what-the-exact-error-is problem. Of course no problem when vLiting from original not-tampered DVD.
And I just want to add before I forgot, before installing Vista SP1 on PC I used to vLiting Vista, vLite crash quite often and produced a BSOD, and seems the WIM filter engine is the cause. After restarting my PC, my Start menu will be rendered useless. But that was fixed in Vista SP1 though.
I've also uploaded the full files/directories listing of the mounted WIM:
http://mihd.net/3l0z7d6
also on the vLited WIM file I already integrated these post-SP1 updates/hotfixes:
- KB905866
- KB937286
- KB938371
- KB941693
- KB943729
- KB947562
- KB947864
- KB948590
- KB948881
- KB950759
- KB950760
- KB950762
- KB951376
- KB951698
- KB9522870 -
so it looks like an selfmade "Audit-Mode" version from Dell. You can't use such a version as source. You must use a clean Image from MS.
no it's not self-made "Audit-Mode" version from Dell. It's the original Vista SP1 DVD from MS. I strip other editions except Ultimate and start integrating hotfixes etc manually (by mounting the WIM image). I also made registry tweaks by loading the hive using regedit.
Can you please post a file list of that distribution, or send it on my PM.You can get the list by typing:
dir "FULL PATH TO DVD OR FOLDER" /b /s>c:\list.txt
since it's my own custom distribution (and vLited), you won't see anything different with any other vLited output
D:\VSP1\Autorun.inf
D:\VSP1\Autounattend.xml
D:\VSP1\boot
D:\VSP1\bootmgr
D:\VSP1\changes.txt
D:\VSP1\efi
D:\VSP1\Last Session.ini
D:\VSP1\sources
D:\VSP1\VistaUltimate.ico
D:\VSP1\boot\bcd
D:\VSP1\boot\boot.sdi
D:\VSP1\boot\bootfix.bin
D:\VSP1\boot\bootsect.exe
D:\VSP1\boot\en-us
D:\VSP1\boot\etfsboot.com
D:\VSP1\boot\fonts
D:\VSP1\boot\memtest.exe
D:\VSP1\boot\en-us\bootsect.exe.mui
D:\VSP1\boot\fonts\wgl4_boot.ttf
D:\VSP1\efi\microsoft
D:\VSP1\efi\microsoft\boot
D:\VSP1\efi\microsoft\boot\bcd
D:\VSP1\efi\microsoft\boot\fonts
D:\VSP1\efi\microsoft\boot\fonts\wgl4_boot.ttf
D:\VSP1\sources\boot.wim
D:\VSP1\sources\install.wim0 -
it the "Red-Edition" a modified Vista DVD from Dell? Does the WIM include all Editions or just the Ultimate.
Yes, the Product (RED) from Dell. Since I don't have money to buy that Dell-Microsoft offer, I think I can recreate one from (RED) resources. I got those "(RED) Edition" resources like sidebar gadgets, wallpapers, DS video etc from google (it's not warez, it's available for free!). The WIM only contain Ultimate image, nothing more or less and it works flawlessly fine before I try to integrate those msu files...
0 -
I've been building my own stripped and up-to-date "Product (RED)" version of my Vista Ultimate. It all goes well until today when I try to integrate the following updates/fixes/patches/hotfixes:
KB950124
KB950125
KB950126
KB951978
KB952709
KB955020the integrating process seems work fine, but when it reach Rebuilding image phase, there's a popup appear says Error while rebuilding image. - The system cannot find the file specified.. What could be the problem? Is it me, vLite or just one of the KBs?
0 -
Nice one, I just noticed that there's a little mistake in description. goto Components -> Hardware Support -> Ports (COM and LPT):
blablabla
...
Needed for:
- Smart Cads
- Infrared
- Printer Support
- Infraredlooks like Infrared is in twice...
0 -
Why do you stupid people talk alot of bulls*** if you can use microsofts wimgapi to do this
because we didn't know C++?
0 -
@sp00f,
yes, it should show description as shown in ur screenshot, but in this matter it is using "Display Discription" and "Display Image" tag instead of "Name" and "Description"!
all these images are custom built of diff. versions.
these "Display Discription" and "Display Image" are in 1.xml of install.wim file , is there any way to extract and rebuild 1.xml?
Amit
wow, where you figure out it uses 1.xml? good then, we just need someone who can extract and rebuild the file now...
0 -
yep, Amit is right. I can't customize the description when I have more that 1 exported image in a WIM. It still display Windows Vista Ultimate for all the image description... I wonder if there's a way to extract the XML file from the WIM, edit and repack it again...
0 -
Yep export all images or just the one you want.
Example :
imagex /export I:\VistaAIO\x86\install.wim 4 I:\VistaAIO\Distribution\SOURCES\install.wim "Windows Vista ULTIMATE (32bit)"
Rename the last part whatever you want.
imagex /export I:\VistaAIO\x86\install.wim 4 I:\VistaAIO\Distribution\SOURCES\install.wim "Windows Vista Ultimate (RED) Edition)"
I use it like this :
imagex /export I:\VistaAIO\x86\install.wim 1 I:\VistaAIO\Distribution\SOURCES\install.wim "Windows Vista BUSINESS (32bit)"
imagex /export I:\VistaAIO\x86\install.wim 2 I:\VistaAIO\Distribution\SOURCES\install.wim "Windows Vista HOMEBASIC (32bit)"
imagex /export I:\VistaAIO\x86\install.wim 3 I:\VistaAIO\Distribution\SOURCES\install.wim "Windows Vista HOMEPREMIUM (32bit)"
imagex /export I:\VistaAIO\x86\install.wim 4 I:\VistaAIO\Distribution\SOURCES\install.wim "Windows Vista ULTIMATE (32bit)"
imagex /export I:\VistaAIO\x64\install.wim 1 I:\VistaAIO\Distribution\SOURCES\install.wim "Windows Vista BUSINESS (64bit)"
imagex /export I:\VistaAIO\x64\install.wim 2 I:\VistaAIO\Distribution\SOURCES\install.wim "Windows Vista HOMEBASIC (64bit)"
imagex /export I:\VistaAIO\x64\install.wim 3 I:\VistaAIO\Distribution\SOURCES\install.wim "Windows Vista HOMEPREMIUM (64bit)"
imagex /export I:\VistaAIO\x64\install.wim 4 I:\VistaAIO\Distribution\SOURCES\install.wim "Windows Vista ULTIMATE (64bit)"that method, AFAIK, only set NAME and DESCRIPTION value, but not DISPLAYNAME and DISPLAYDESCRIPTION value... correct me if I'm wrong...
0 -
Method 1 - Limited:
is there any other method?
0 -
you're welcomed, I just have one last problem, the background image when first entering setup and right before setup restart PC, it still the default image, I've changed anywhere I think the image could be but same...
0 -
Edit spWizImg*.dll in source folder and replace the last bitmap object in the DLL.
0
Multiple questions on customizing an SP1 pre-integrated Vista DVD
in vLite
Posted
As I didn't play with vLite much, I can only put my thought about question no 6: If you select an application/feature from Compatibility window, vLite will hide that options in components removal list, so you won't accidently removed anything needed to run the feature/application successfully.