خرطت أن يركّب [ويندووس] 7, [فيستا] أو نادلة 2008 على حاسوب أو آلة فعليّة [ويث لسّ ثن] 512 [مب] [رم مموري]
رأيت رسميّا [ويندووس] 7, [ويندووس] [فيستا] و [ويندووس] نادلة 2008 أدنى نظامة جهاز مواصفات ( [ويندووس] 7 نظامة متطلبات و [ويندووس] [فيستا] نظامة متطلبات) يتطلّب أكثر من 512 [مب] من مطرقة ذاكرة طبيعيّة [, ثوو] مكروسوفت يوصي 1 [غب] ذاكرة أدنى كثير إنتاج سيناريوهات. بما أنّ مثل هذا, ال [إينستلّ] لا يسمح ساحرة [ستثب] عملية أن يذهب من خلال عندما ال [سستم مموري] أقلّ من 512 [مب] عندما يركّب [ويندووس] 7, [ويندووس] [فيستا] و [ويندووس] نادلة 2008 على [بك] حاسوب أو آلة فعليّة. التركيب سيتوقّف ساحرة وسيجبر موقف تجهيز عملية مع ال [إرّور مسّج] تالي.
[ويندووس] كشف أنّ يتلقّى <هذا حاسوب 128 | 192 | 256 | 320> تطلّبت [مب] من مطرقة, غير أنّ 512 [مب] لتجهيز. تجهيز يستطيع لا يباشر.
عكس إلى إعتقاد شعبيّة, التجهيز عملية من [ويندووس] [أبرت سستم] يمكن تطلّبت [إفن موش] ذاكرة أن يحمّل ومهّدت من [بوست-ينستلّأيشن] نظامة جارية. التجهيز سيخلق روتين يبدأ من [دفد] أسطوانة أو [إيس] [رم ديسك], أيّ يقصّر أكثر من 128 [مب] من مطرقة. هذا حقيقة يضطرّ كنت أخذت بطاقة عندما يحاول أن يركّب [ويندووس] 7, [ويندووس] [فيستا] أو [ويندووس] نادلة 2008 على حاسوب أو آلة فعليّة [ويث لسّ ثن] 512 [مب] من مطرقة, وقد أوصى هو أن يتلقّى على الأقلّ 256 [مب] من مطرقة [إفن فتر] يستعمل الفأس أدناه أن يضمن تركيب عملية يستطيع كنت يحمّل [بروبرل]. أخرى, أخطاء مختلفة مثل "[رمديسك] أداة خلق [فيلد] واجبة إلى ذاكرة غير كاف" ب "[ويندووس] جزمة مديرة", أو ببساطة يجمّد وموقف يستجيب عندما يمهّد [دفد].
هكذا, كيف أن يركّب [ويندووس] 7, [ويندووس] [فيستا] و [ويندووس] نادلة 2008 على نظامة أو [فم] مع فقط 256 [مب] إلى 512 [مب] من [رم مموري]? هناك قليل من [ووركرووند] إلى يستطيع كنت استعملت أن يركّب [ويندووس] [أبرت سستم] حتّى دون 512 [مب] مطرقة.
طريقة 1: 384 [مب] من مطرقة أن يركض تركيب تجهيز
Although the Windows setup process dialog message indicating at least 512 MB of RAM is required, in actual it will only look for available memory of around 384 MB (373 MB of RAM is workable in the case of Windows 7). Thus, end-user can easily add an additional piece of physical RAM into RAM slot to reach this threshold, or even easier in virtual machine, increase the allocated RAM slightly to match 384 MB level.
Method 2: Install With Required RAM Size and Reduce Memory Amount After Installation
While setup installation of Windows 7, Windows Vista and Windows Server 2008 requires 512 MB of memory to proceed, but that does stop user to reduce amount of RAM memory available to the system after installation completed. So, this workaround requires user to increase the amount of physical or virtual RAM to 512 MB (adding memory stick) in order to fulfill setup requirement, and then reduce the memory size to lower level (remove the added memory stick) once installation is completed. This workaround is especially easy for virtual machine, which more likely encounter low memory issue.
Method 3: Patch winsetup.dll Hack
The system check for RAM size and its stop installation routine is coded in winsetup.dll file on the DVD disc or ISO image. Follow the steps below to patch winsetup.dll to bypass the RAM memory check during setup installation of Windows 7, Windows Vista and Windows Server 2008.
Note: Only works on 32-bit (x86) version.
- Copy the content of DVD installation disc media, or extract the contents of DVD ISO image to hard disk drive.
- Download and install any HEX editor such as AptEdit Pro, WinHEX and Notepad++ (a Notepad alternative) with HEX Editor plugin.
- Use the HEX editor to open winsetup.dll located inside the /source/ folder of the copied installation files.
- Search or find the following HEX (hexadecimal) string:
77073D7801
- Modify the HEX string to replace and overwrite it with the following HEX code:
E90400000
- Save the modified winsetup.dll file.
- Run the setup.exe from the installation files copied to hard disk. For user who wants to start installation from bootable DVD instead, replace the winsetup.dll in the ISO with patched version, and then burn the ISO to disc.
Do note that although Windows can still run at less than mandatory required RAM memory, the performance of the system will take serious hit. With ridiculously low amount of memory, Windows Boot Manager may simply fail to load and stop with “Windows failed to start” or “No physical memory is available at the location required for the Windows Boot Manager. The system can not continue” error message, if not system driver or registry file is missing or corrupt message.
IMPORTANT: The page is machine translated and provided "as is" without warranty. Machine translation may be difficult to understand. Please refer to original English article whenever possible.
Related Articles
- Try Out and Install Windows Vista in Virtual Machine with Virtual PC 2007 and VMWare Server
- Patch to Use and Install Windows Vista on Computer with Only 256MB Memory
- Workaround Fix to Install Virtual PC Additions on Windows Server 2008 Core
- Official Registry Hack Script to Install Windows Server 2008 and Vista SP2 Beta Build 16497 (CPP) via Windows Update
- How to Install Windows 7 or Windows Vista on Physical Machine Without DVD Media
- Install Windows Vista in Virtual PC 2007 without DVD media or DVD-ROM Drive
- Virtual PC for Windows 7 (for Virtual Machine or XP Mode) Free Download (KB958559)
- Hack and Workaround to Clean or Fresh Install Windows Vista with Upgrade License DVD
- Windows Server 2008 Evaluation Virtual Hard Drive (VHD) Images Free Download (for VS2005 and Hyper-V)
- How to Install and Use Windows Server 2008 240 Days for Free










































July 28th, 2009 11:46
Even you can install windows on Virtual Machine with 256 or 512 MB RAM Memory, the computer will running slow.
July 28th, 2009 04:43
I installed Windows 7 RTM on an 8 year old PC which has a 1.4GHZ P4 and 384 MB RDRAM. This makes it about as ‘powerful’ as a Netbook from early 2008, but with too little RAM.
Installation went without a hitch, as Windows 7 will not complain. While Vista was slow as molasses on that machine, Windows 7 runs quite well using initially about 250 MB of RAM. It is very usable for surfing with Firefox and writing with OO.