willharr

Member
  • Content count

    4
  • Joined

  • Last visited

Community Reputation

0 Neutral

About willharr

Profile Information

  • OS
    none specified
  • Country
  1. CHECK THIS OUT !!!! http://answers.microsoft.com/en-us/feedback/forum/fdbk_commsite-feedback_other/information-about-the-windows-10-start-button-not/49b7a77f-5faf-48d6-9fdd-dfd9960b51fc Thank You For Reading, Sincerely, willharr MCTS Windows Server 2008/General Researcher
  2. Here It Is Y'all, It's On And Popping Out Da Virtual Box Fresh For The New Year 2013. First Make Sure That Your Flash Drive Is Bootable By: [*]Opening CMD as Admin [*]Running Diskpart [*]List Disk [*]Select Flash Drive Letter [*]Clean [*]Create Partition Primary [*]Select Partition 1 [*]Active [*]Format fs=NTFS [*]Assign [*]Exit Diskpart But Keep CMD Open [*]Insert Your Windows 7 DVD Into The Optical Drive [*]Type ----> D: CD Boot and Press Enter (Type D Or Whatever Letter Your Optical Drive Is) [*]Type ----------> CD Boot -------> Example - D:\>CD Boot [*]Then Type The Command bootsect /nt60 (Flash Drive Letter)E: ----------------> Example - D:\Boot>BOOTSECT /NT60 E: Now The Flash Drive Is Bootable "I Thought I Heard The Funny Looking Guy Say That". Make Sure That You Have Installed All Of The Drivers And Patche's N Thang's For Virtual Box "They Really Come In Handy". Make Sure That You Configure The Proper USB Settings For Virtual Box. Also Make Sure That Virtual Box Is Set To Detect The USB Flash Drive As Soon As The Guest Starts Up. Also, Make Sure That Your Answer File Is Configured For The Correct Bios Settings ----->Check This Out -------------------------------> http://technet.microsoft.com/en-us/library/dd744509(v=ws.10).aspx Now, Let's Get Started With This Answer File Business. First We Want To Make Sure That We've Got A Nice Clean Install.wim. The Next Part Is The Tricky Part. People Always Say That The Basic Configuration Answer File Will Do The Trick, Well That's Not The Case In The Mysterious Virtual Box Scenario. Windows Itself Acts Funny Sometimes And Won't Let You Install The OS On An Unpartitioned Drive, So, I Had A Funny Feeling That Maybe Virtual Box Was Shedding Light On The Darker Side Of Windows, And Then, Configured My Answer File To Partition The Virtual Box Drive For The Installation. Under Image Install/OS Install I Configured Install To Disk ID [0], Partition ID [1], And Install To Available Partition [False] (Most Of The Time Setting This Configuration To [True] Is Perfect But Not Tonight). "Tricky Part" Then I Configured Disk Configuration/Disk WCM:Action=[Modify] (The Reason Why I Say This Part Is Tricky Is Because Sometimes Windows Itself Has Mood Swings And Wont Let You Install The OS On An Unpartitioned Disk And It Could Be True That Virtual Box Exposes This Side Of Windows Since I've Configured The Disk Configuration/Disk WCM:Action Pass To [Modify] And Found Complete Closure To This Particular Issue. During The Previous Months I Had Found Myself Setting This Pass To [add]. The Trick Is You May Never Find Out Whats Going On If You Dont Understand Whats Going On). Next I Configured Create Partition WCM:Action=[Add], Type=Primary, Order=1, And Disk ID=0. Now The Answer File Is Configured To Modify The Drive By Applying A Partition To Install The OS On. Works Like A Charm, Time To Go To Sleep. Take A Look At My Answer File For Specific Details. <?xml version="1.0" encoding="UTF-8"?> -<unattend xmlns="urn:schemas-microsoft-com:unattend"> -<settings pass="windowsPE"> -<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema- instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-International-Core-WinPE"> -<SetupUILanguage> <UILanguage>en-us</UILanguage> </SetupUILanguage> <UserLocale>en-us</UserLocale> <UILanguage>en-us</UILanguage> <SystemLocale>en-us</SystemLocale> <InputLocale>en-us</InputLocale> </component> -<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema- instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-Setup"> -<UserData> <AcceptEula>true</AcceptEula> <FullName>will</FullName> </UserData> -<ImageInstall> -<OSImage> -<InstallTo> <DiskID>0</DiskID> <PartitionID>1</PartitionID> </InstallTo> <InstallToAvailablePartition>false</InstallToAvailablePartition> <WillShowUI>OnError</WillShowUI> </OSImage> </ImageInstall> -<DiskConfiguration> -<Disk wcm:action="modify"> -<CreatePartitions> -<CreatePartition wcm:action="add"> <Type>Primary</Type> <Size>7000</Size> <Order>1</Order> </CreatePartition> </CreatePartitions> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> </Disk> <WillShowUI>OnError</WillShowUI> </DiskConfiguration> <Restart>Restart</Restart> <EnableNetwork>true</EnableNetwork> <EnableFirewall>true</EnableFirewall> </component> </settings> -<settings pass="oobeSystem"> -<component language="neutral" xmlns:xsi="http://www.w3.org/2001/XMLSchema- instance" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" processorArchitecture="x86" name="Microsoft-Windows-Shell-Setup"> -<UserAccounts> -<LocalAccounts> -<LocalAccount wcm:action="add"> <Name>will</Name> <DisplayName>will</DisplayName> </LocalAccount> </LocalAccounts> </UserAccounts> <BluetoothTaskbarIconEnabled>true</BluetoothTaskbarIconEnabled> <DisableAutoDaylightTimeSet>false</DisableAutoDaylightTimeSet> <DoNotCleanTaskBar>true</DoNotCleanTaskBar> <TimeZone>central</TimeZone> </component> </settings> <cpi:offlineImage xmlns:cpi="urn:schemas-microsoft-com:cpi" cpi:source="wim:c:/flashfiles/sources/install.wim#Windows 7 ENTERPRISE"/> </unattend> It's Been Great; Now Give Me My 5 Thousand Dollars!! Thank You, WillHarr MCTS Configuring Windows Server 2008 Active Directory
  3. fellas, fellas, fellas, take your answer file and juice it up anyway that you like. it will not work properly in virtual box. i will assure you. the reason for this i'm not quite sure. however i've had much success in vmware with just a basic configuration answer file.
  4. same video, same virtual box, same os, same problem, i may have to agree with tripredacus after maintenancing my answer file a few times and getting an xml message in the wsim stating ( the catalog file associated with the windows image windows 7 enterprise (catalog) is out of date ). the funny thing is that the answer file and disk work out fine on vmware at school. or may be that message could just mean that everybody in the school has wore out the disk. any comments??? **update** - secondly, virtual box has recently recieved many various updated versions, drivers, service packs, patches, etc. due to this fact, i strongly believe that all the recent revisions to virtual box is causing certain wim files to become outdated. just think about it, the same simple answer file works fine in vm ware.