killerb255
Content Type
Profiles
Forums
Events
Posts posted by killerb255
-
-
Make_PE3 will make 7PE with built-in msi support.
You will find in Make_PE3\MULTI\SxS_Fix_Win7PE folder info and file SxS_7PE_SFX.exe to fix the side by side errors.
Yes, but Make_PE3 doesn't support SP1 or IE9...
0 -
Wimb:
Will Make_PE3 be updated to be compatible with a Windows 7 SP1 source and Internet Explorer 9? Using Windows 7 SP1/IE9 results in an RTM Make_PE3 build and a broken Internet Explorer (the icons look as if IE9 ported over, but opening up IE9 results in the browser opening and closing after about 1/2 second...)
0 -
Start -> Run -> type in msconfig and click OK.
Go to the "Boot" tab and click "Advanced Options."
Is "Maximum Memory" checked? If so, uncheck it.
0 -
So...what's the minimum amount of RAM to fire up this bad boy? Is it still 512 MB (like a basic PE build) or is it something north of that?
0 -
how could I create a add-on for it? seems that the catalog file and update.inf should be modified, but how?
thanks
I didn't manually copy files at all. Instead, I created a batch file to swap update.inf files:
Maybe that'll help you integrate it...
0 -
I'm sure it's going to involve some serious BCD editing...
Probably somewhere between the time you unmount the PE image and make an ISO, you would copy your Vista source files to the same source. Edit the BCD from there to determine which starts up (I'm sure you could even make a 30 second menu if you wanted to).
This should work in theory. How to do it in practice...more research needed...
I'm not sure if the wim files need to be consolidated or if you could use two wim files...
0 -
Roger that.
I'll do so once I get a fresh source going as well as a virtual machine to test.
0 -
It is possible to make a WinPE 2.1 flat file disc.
Follow the instructions here, for the most part (special thanks to paxamime for going through the trouble to make those batch files in the first place!):
http://www.msfn.org/board/index.php?s=&...st&p=577244
However, you will need to make these modifications:
1) On 2Mount.bat, change boot.wim to winpe.wim.
2) Create a new batch to run after 5Unmount.bat called 6Apply.bat with the following:
REM 6-Apply.bat
REM This will apply the winpe.wim image to a new directory called winpe_flat.
REM No mounting or unmounting of images are necessary in a flat file structure.
%systemdrive%
echo Applying the current winpe.wim to C:\PE\winpe_flat to create a flat-file structure.
mkdir c:\PE\winpe_flat
cd \
cd %programfiles%\Windows AIK\Tools\x86
ImageX /apply c:\PE\winpe_x86\winpe.wim 1 c:\PE\winpe_flat
echo Adding a boot directory to C:\PE\winpe_flat
mkdir c:\PE\winpe_flat\boot
xcopy c:\PE\winpe_x86\ISO\boot]*.* /e /f c:\PE\winpe_flat\boot\
pause3) Make a 7Bootloader.bat file with the following contents:
@echo off
echo 7-Bootloader.bat
echo This will create a new BCD database for your flat-file PE disc.
:STEP1
set peiso=%systemdrive%\PE\winpe_flat
goto STEP2
:STEP2
echo Deleting the existing BCD directory and preparing to create a new one.
del C:\PE\winpe_flat\boot /q
goto STEP3
:STEP3
echo Creating a new bcd
Bcdedit /createstore %peiso%\boot\BCD
Bcdedit /store %peiso%\boot\BCD /create {bootmgr} /d "Boot Manager"
Bcdedit /store %peiso%\boot\BCD /set {bootmgr} device boot
Bcdedit /store %peiso%\boot\BCD /create /d "WinPE" /application OSLoader > guid.txt
goto STEP4
:STEP4
echo The previous command returns a GUID value.
echo The next command parses the GUID and adds it to the remaining commands.
for /f "tokens=3" %%h in (guid.txt) do (set guid=%%h)
goto STEP5
:STEP5
Bcdedit /store %peiso%\boot\BCD /set %guid% osdevice boot
Bcdedit /store %peiso%\boot\BCD /set %guid% device boot
Bcdedit /store %peiso%\boot\BCD /set %guid% path \windows\system32\winload.exe
Bcdedit /store %peiso%\boot\BCD /set %guid% systemroot \windows
Bcdedit /store %peiso%\boot\BCD /set %guid% winpe yes
Bcdedit /store %peiso%\boot\BCD /set %guid% detecthal yes
Bcdedit /store %peiso%\boot\BCD /displayorder %guid% /addlast
echo The custom boot loader has been created.
pause4) Change 6MakeISO.bat to 8MakeISO.bat.
5) Burn ISO to CD.
6) Boot from it.
You will NOT be asked to "Press any key to boot from CD or DVD..."0 -
One thing I have noticed after integrating 955839 is that, although the time zone is correct (in my case, it's "Central Time (U.S. and Canada)"), a fresh install of XP using the nLite'd source during the Extended Daylight Saving Time periods:
1) 2nd week of March thru 1st week of April
or
2) Last week of October thru 1st week of November
...results in "Central Standard Time" instead of "Central Daylight Time."
If I try to reinstall 955839, I get an error stating that the patch has already been installed or has been superseded. However, an install of 951072v2 works and correctly changes the Time Zones...
Any ideas?
0 -
You shouldn't have to use a GUID. By default, PE assigns the first NIC the name "Local Area Connection," the second "Local Area Connection 2," etc.
0 -
has anybody done this with the vista sp1 dvds ? everytime i try it errors out saying file is larger than 4g
Are you using single or dual-layer DVDs?
On a side note, has anyone tried integrating the Vista Enterprise DVDs (both 32 and 64-bit) into one installer? Same instructions, except you're actually merging four DVDs (retail 32-bit, retail 64-bit, Enterprise 32-bit, and Enterprise 64-bit) instead of two.
EDIT: I've done so recently, and it works great!
10 different Vistas (Home Basic, Home Premium, Business, Enterprise, and Ultimate x86 and the same five x64)--all install just fine!
0 -
Use this command:
netsh interface set ipv4 address "[name of the connection]" static [iP address] [subnet mask] [default gateway] [metric number]
For example, to set a static IP to two NICs, you would use two commands:
netsh interface set ipv4 address "Local Area Connection" static 123.45.67.89 255.255.255.0 123.45.67.81 1
netsh interface set ipv4 address "Local Area Connection 2" static 123.45.67.88 255.255.255.0 123.45.67.81 2
Substitute the IP addresses, subnet mask, and default gateway you want accordingly.
0 -
Finally, people are resistant to change. They are afraid of it, particularly where computers are concerned.
That's just human nature. The more we learn, the less we want to learn, and the more we want to apply what we know.
Change stimulates fear. After all, fear is nothing more than a perceived loss of control. When things change, we don't feel as "in control" as we did beforehand.
However, when there is no change at all, people end up lamenting in their comfort zones, even if that zone is a danger zone of sorts. Abused women are a perfect example of this. They would rather keep things the way they are, even if their lives are at risk, than to remove themselves from the situation and deal with the unknown--something that they don't think they have control over.
Bottom line: Zero change is unhealthy. Change for the sake of change does more harm than good (dealing with the resistance and having little to gain from it).
Were the Windows 7 UI changes simply "change for the sake of change"? To many, yes it is. To some, not really.
Being a veteran in the IT business, I'm sure you remember people complaining about the changes in Windows being too minute. In other words, a new version of Windows is pointless to the "S" (sensing) personalities out there that learn solely by their five senses (sight, hearing, taste, touch, smell). To an S personality, Windows 95 and Windows 98 were pretty much one and the same. The "N" (intuitive) personalities familiar with both OSes knew the differences, though (for better or worse): better networking support, FAT32 support out of the box, better USB support, integrated Internet Explorer...
So in reality, the Windows 7 UI changes were most likely to convince the S personalities out there that Windows 7 is "new," "different enough from Vista," and "different enough from previous versions of Windows in general."
not just moving but busting up the way profiles are handled,These things really are necessary evils with the new 2.x profiles. The old profile storage system was slow, didn't roam well, and could cause (lots) of problems with roaming users and terminal server-heavy environments (this ultimately stemmed from the way winlogon and the group policy engines were designed). Again, a pain, but a necessary evil to make differential profile roaming and removing the winlogon handles to locations in the user's profile (especially if it was stored remotely) needed to be done. They were problems since NT4, and finally addressed.
QFT!!!!
I can't count how many times I've had to rebuild Windows 2000 and XP roaming profiles!!! I haven't dealt with a single corrupt Windows Vista roaming profile yet!
0 -
At least this is an easy way to distinguish the beta testers from the leeches...
0 -
So Windows 7 defaults to GPT? No option for MBR?
0 -
@riksox:
Use PE 2.1 instead of 2.0 and see if you get a different result...
0 -
WAIK for Windows 7 = Windows PE 2.2?
0 -
1) Just three versions: Home, Professional, and Ultimate.
BTW, XP actually had a lot of versions as well:
Windows XP Home Edition
Windows XP Professional Edition
Windows XP Media Center Edition
Windows XP Tablet PC Edition
Windows XP Professional x64 Edition
Windows XP Professional ("Corporate/VLK") Edition
The last four were OEM and/or VLK only. Vista's versions were more public, hence the confusion.
Proposed public versions of 7:
Windows 7 Home Edition (x86, x64)
Windows 7 Professional Edition (x86, x64)
Windows 7 Ultimate Edition (x86, x84)
Home replaces Vista Home Basic and Home Premium
Professional replaces Business
Ultimate corresponds with Vista Ultimate (hopefully with lower pricing...)
Proposed private versions of 7 (OEM, VLK, etc.)
Windows 7 Enterprise (x86, x64)
Enterprise corresponds with Vista Enterprise. Just don't advertise it to the general public...
2) Modular install, a la Windows Server 2008 (or even Windows 98!)
Pick the stuff you want. If the stuff you want has dependencies, those will be selected for you.
However, there are things I DO like about Windows 7 that are already there:
1) Optimized! It can run on a Netbook! (THIS is the reason why Windows 7 is not 64-bit only! Vista can't run on Netbooks, ya know...)
2) Sidebar gadgets are integrated with the Desktop instead of having a separate app that sucks up more RAM than it should.
3) User Account Control is more flexible. Instead of "all or nothing," you can control how much or little nagging you want...
4) Media Center--supports QAM and H.264...about ****ing time!
5) Faster startup and shutdown!
0 -
For some reason, it seems that the Vista Experience memory score favors AMD systems. Maybe it's because of the built-in memory controller in the CPU?
My cousin and I both have 8 GB of the exact same RAM (GSkill DDR2800, 4-4-4-12).
He has a Phenom 9600
I have a Core 2 Quad Q6600
Both have Vista x64.
He has a 5.9
I have a 5.4
0 -
Can it create a flat-file structured PE? That is, one that doesn't create a RAM drive?
0 -
0
-
You forgot to slipstream the Dell AHCI drivers into your source.
Otherwise, disable AHCI in the BIOS (it's under "SATA operation") and switch it to ATA mode.
0 -
Correct.
XP sees SATA drives as "removable" or "hot-swappable," even if your boot drive is a SATA drive...
0 -
It'd be nice if you post the make and model of your laptop...
0
WinPE Diskpart problem
in Windows PE
Posted
Edit the registry of your PE before running the diskpart command: