|
|
本帖最后由 liuzhaoyzz 于 2021-1-17 12:18 编辑
1KRAMOS4.0.0-English
【RAMOS一键批处理多合一V4.0.0】在线制作P驱R驱F驱内存系统工具（英文版）
下载地址：https://www.lanzous.com/b00n7bcqf
有几个外国的网友活跃在无忧启动论坛，例如巴基斯坦的maanu，越南的2012mshs，土耳其的gazi06......等等等等，有些网友很早就关注了芈员外的一键RAMOS作品，他们希望能直接用芈员外的一键RAMOS来制作，员外太忙，一个人撑起了一键RAMOS的半边天，也太累，一键RAMOS现在已经有3000行代码需要维护，芈员外的一键RAMOS在英文版系统中会有乱码现象，我改了下里面的提示，支持英文，也算是为芈员外分担点工作量，为RAMOS添砖加瓦吧。
作品是他原创的作品，我已提交给他，最终版本，以他的发布为准哦！顺便说下，英文版提示是英文版，也可用于中文windows系统哦。
论坛里不乏批处理的高手，任何人写的程序或者代码都有可能会有bug，希望借此抛砖引玉，引来大家共同查找bug，反馈问题，形成RAMOS欣欣向荣的好现象！
为了方便英文版交流反馈，我重新开了个帖子，当然你也可以去芈员外那个主帖子去反馈。
中文版说明文件太多太长，不好翻译，打开说明文件乱码的可以在控制面板改所在地区重启：
control panel→search language→Regon and language→Administrative→Change system locate→select chinesesimplified,PRC）and reboot.
Brief production instructions(Google translation):
1. Software and hardware requirements:
(1)WIN7 and above operating system, 32/64 bit can be installed in physical drive C or VHD, physical memory is 3G or more than C drive space, physical memory is recommended 8G or above ( The bigger the better), it is recommended to use a streamlined system. It is recommended to install it in VHD with WINNTSETUP.If the total size of vhd is smaller than the memory, any mode can be experienced. It is recommended to determine the vhd size according to your own windows system, application software and memory size, and don't set it too large. If the vhd is too large, it will be slow to make and require more temporary space.
(2)XP/2003 operating system, 32/64 bit, only NTFS compression mode can be selected, the system can be installed on the physical disk C , the physical memory is 2G or more larger than the disk C, and the physical memory is recommended 4G or above. The bigger the better, it is recommended to use a streamlined system.
Note: Regardless of the operating system, it is recommended that the original system do not have hidden partitions that affect booting. For example, some computer boot partitions (partitions containing ntldr/bootmgr) are hidden, and the operating system is installed in another partition. It is suggest that the partition is merged with the partition where the operating system is located, activation the partition, and assign the drive letter. Otherwise, there may be a problem to write the boot of the RAMOS; in addition, the vdf is placed in the primary partition as much as possible, for the logical partition grub4dos placed in the back may not be found.
2. Mode selection: Traditional BIOS+MBR hard disk with large memory recommend using rich-2 double image mode, and general users recommend using fool mode; Users of UEFI+GPT hard disk +64-bit system with large memory recommend using rich-0 g4e/grub2_UEFI+Primo local dual image mode, while general users recommend using 2-g4e/grub2_UEFI+Primo-SCSI dual image mode. If there is a problem, you can try single mirror mode.
3. Production process: close the original system virtual memory and hibernation files (recommended), restart the computer normally, then put the [one key batch 3.7.3] batch entire folder into the drive letter outside the system C drive, and ensure that the drive letter has enough hard disk space to store the mirrored backup ramos.sna and compact.wim temporary files of the used space of the C drive. After restarting, right click on the [one key batch 4.0.0] batch in the original system. Run as an administrator, the batch will automatically install the primo or ramdisk driver or Firadisk driver, and make the relevant vdf image.
Save the VDF to the D drive or the E drive. The input path is VDF\CPRAMOS. The batch process will automatically create the RAMOS and restart it automatically.
4.Speed test to ensure running in RAMOS. You can use CrystalDiskMark or AS SSD Benchmark, test your drive C and the drive D for Comparison, confirmed that you entered the RAMOS. The RAMOS Seq has a minimum of 1000MB/s.
5. Start --> All Programs --> Backup --> backup batch can be used to perform one-button hot backup (except for distant mode).
6. Install the driver in the original system as much as possible. After installing the driver, the hot backup may cause the RAMOS fail to start. When the RAMOS fail to start, it can be re-created.
7. A few software like qq maybe can't be started in some modes, you can use green software instead.
8. 1KRAMOS4.0.0-English was written by y7y007 and liuzhaoyzz from bbs.wuyou.net,You can feedback in the forum's essence post:
RAMOS-wuyou: http://bbs.wuyou.net/forum.php?m ... p;fid=87&page=1
To RAMOS newbie: http://bbs.wuyou.net/forum.php?m ... &extra=page%3D1
WINNTSETUP setup system(for RAMOS newbie): http://bbs.wuyou.net/forum.php?m ... &extra=page%3D1
1K RAMOS Chinese: http://bbs.wuyou.net/forum.php?m ... &extra=page%3D1
1K RAMOS English: http://bbs.wuyou.net/forum.php?m ... &extra=page%3D1
Romex Software - Primo Ramdisk | PrimoCache | VSuite Ramdisk | FancyCache, Speed Up Your Computer http://www.romexsoftware.com/en-us/index.html
Attention：
(1)RAMOS newbie can choose fool mode; rich mode is suitable for large memroy;NTFS compression mode supports XP/03 better.
(2)In the rich mode,the physical C drive of the original system or the total number of VHD disks must be less than the total memory, because the current version of the drive snapshot can only be cloned from a small partition to a large partition; when cloning from a large partition to a small partition, capacity requires at least a certain amount of space, and strange problems may occur. Therefore, please reduce the total size of the physical C drive or VHD drive (not to reduce the used space!). Also for 64-bit systems, don't run a the batch from a third-party 32-bit file browser, because 32-bit file browsers don't have direct access to certain windows and registry files, recommended from Windows Explorer. Right click to run as a administrator! The read and write privilege of some files go beyond the ability of Nsudo.
(3)Primo drive RAMOS local single mirror mode [complete single image, some memory support dynamic recovery, need large memory, faster production], has good compatibility, pay attention to the mode requires the original C disk total size (not used space!) is less than memory, and the available memory should be large enough to create a primo memory disk. Note that the larger the memory disk allocation, the slower to boot windows, because more full mirror data needs to be loaded into the memory. The startup speed depends on the size of the vdf and the vdf reading speed of the storage.
(4)After running the RPIO and RPCP schemes in old batch, the primo memory disk of the original system must be deleted before the virtual memory of the primo memory disk is closed. My computer-->right-click Properties-->Advanced System Settings-->Advanced Tab-->Settings-->Advanced-->Select No Pagination File --> set and confirm, then restart normally, you can delete the memory disk after rebooting, it is better to restart your PC after deletion, otherwise it may affect other mode.
Change logs:
[1KRAMOS4.0.0-English]
1. considering copyright issues, from V4.0.0, primo software is no longer packaged. please install genuine primo ramdisk software by yourself and then run the batch as administrator!
(1) purchase Primo Ramdisk license https://www.romexsoftware.com/zh-cn/primo-ramdisk/purchase.html
(2) Comparison of version features https://www.romexsoftware.com/zh-cn/primo-ramdisk/features.html
Hereby solemnly declare that all legal responsibilities brought by users using pirated and cracked software have nothing to do with one-click tools!
Thanks to Romex for providing excellent high-speed memory disk software!
2. Version V4.0.0 is a major update of UEFI-primo-RAMOS. From this version, all schemes driven by Microsoft ramdisk.sys will not be updated as abandoned schemes.
In UEFI production mode, grub4dos_UEFI-primo-RAMOS and grub2_UEFI-primo-RAMOS startup schemes are added, which is a full memory scheme that does not depend on Microsoft Ramdisk.sys driver but only depends on primo driver, and supports WIN7 8 10, including single mirror mode and double mirror mode. Because g4e/grub2 did not pay Microsoft a protection fee, it is necessary to turn off the secure boot in BIOS settings, and the scheme of bypassing the secure boot is beyond the scope of this paper.
(1) when ntfs_x64.efi is abandoned, grub2+ntboot has nailed WIN7 8 10 single image and double image, and WIN7 8.1 10 double image mode supports no compression, compact compression and wimboot compression.
(2) with ntfs_x64.efi preserved, map of g4e/grub2 has nailed WIN7 8 10 single image and double image, and WIN7 8.1 10 double image mode supports no compression, compact compression and wimboot compression.
It is suggested that the original system should be installed in a fixed-size vhd. The size of vhd should be determined according to the windows system, application software and memory size. If the total size of VHD is smaller than memory, any mode can be experienced. It is suggested that the VHD size should be determined according to its own windows system, application software and memory size, and should not be set too large. If the VHD is too large, it will be slow to make and require more temporary space. MBR+NTFS single partition is recommended in VHD. G4e/grub2 menu is /EFI/grub/menu.lst and /boot/grub/grub.cfg of boot partition respectively, which need utf-8 without BOM encoding format. It should be noted that the single mirror mode generally requires the total size of vdf to be larger than the total size of vhd.
After making, press F12/F8/F9/F11/ESC and other one-time startup hotkeys to start from g4e/grub2, or you can enter UEFI settings and set your favorite startup item as the first one.
-thanks to Wintoflash, 2011yaya2007777, Kai Schtrom, sunsea, Juma 12345678, alacran, xyzy1008, Xianglang, Wuwuzz, t5481194, pauly, y7y007, liuzhaoyzz and so on ...
3. Mount the boot partition with smartmountfirmware of CodeHz and assign the drive letter. If the program is killed by 360, automatically look for \EFI\Microsoft\Boot\bootmgfw.efi from back to front, and take the first one found as a prompt item. http://bbs.wuyou.net/forum.php?m ... p;tid=423468-Thanks to the rookie of CodeHz, 527104427, nttwqz, plusv and dos!
4. Replace sed version with version 4.7.
5. mount ESP partition with FindESP (smartmountfirmware of CodeHz has been used instead). http://bbs.wuyou.net/forum.php?mod=viewthread&tid=374167----感谢guyue2011！
6. Fix the problem of copying \EFI and \BOOT folders to ESP partition. -thanks to d634655401, sevenyu, xuxuezeng, xiaowu2000 and diwu2005 for their feedback.
7. After selecting the production mode, it will be displayed at the top of the screen, which is convenient to locate the problem quickly.
8. grub2-ntboot mode uses /EFI/Microsoft/boot/bootmgfw.efi of virtual disk, so this file must exist. if it does not exist, use bcdboot command to repair the boot in advance.
9. grub2 resolution is set to 1024x768 first, so as to avoid over-underestimating the high-resolution screen fonts. Please modify it manually in the boot partition /boot/grub/grub.cfg, and add a sentence set gfxmode = 1024x768,800x600, auto before terminal_output gfxterm. It should be noted that a new version of g4e/grub2 may be released. bootx64.efi and grubx64.efi of g4e/grub2 need to be updated manually by yourself. One key will determine whether the boot partition file exists, and if it exists, it will be skipped automatically. The purpose of this is to avoid replacing the file in your local hard disk boot partition with the old version in one key. One key assumes that G4E/GRUB is the latest version in your computer.
10. using GRLDR_Edit_v5.0.2, a menu40.hex.gz with 40*40 font is made, which can be used for computers with ultra-high definition resolution. http://bbs.wuyou.net/forum.php?mod=viewthread&tid=376003
/EFI/grub/menu.lst in front of #font /EFI/grub/unifont.hex.gz plus English #, comment it out, and change it to the following:
graphicsmode -1 800:7680
font --font-high=40 /efi/grub/menu40.hex.gz
-thank you fuldho!
11. adopt the cs3 version g4e dated January 8th, 2021,
http://bbs.wuyou.net/forum.php?m ... &fromuid=298214
graphicsmode -1 800 is used to solve the problem of high-resolution computer crashing into graphics mode. -thanks to 2011yaya2007777 and sevenyu!
12. the single drive scheme of g4e/grub2_UEFI+Primo is specified in the menu entry. -Thanks to ko20010214 and xuxuezeng for their suggestions and feedback!
13. under UEFI, judge whether the safe start is on, and give a prompt if it is. -thanks to adef and Wintoflash!
14. modify the vdf date format to ensure that it can adapt to various languages. ----liuzhaoyzz
Change logs:
[1KRAMOS3.8.7-English]
1. microsoft Ramdisk dirver mode (including RPIO, RPCP, RPWimboot, etc. under BIOS / UEFI). Win8 only installs startisback and does not install winxshell.
Based on the Microsoft ramdisk driver mode, the modification looks like this:
(1) There is no problem with the start menu, wifi, and volume in WIN7. No correction is required.
(2) In WIN8.1, there is no problem with the wifi and volume in the tray area, that is, there is a problem with the right-click on the start menu, only startisback is required, and no winxshell correction is required.
(3) In WIN10, left-click on the start menu has problems, right-click has no problems, left-click on wifi and volume in the tray area is invalid, and it needs startisback + winxshell to fix it.
For UEFI-WIN10, it is recommended to turn off the WIFI and volume icons in the original tray area on the original system, otherwise the icon will be duplicates (the system and winxshell). A prompt has been given on the UEFI-WIN10 interface.
How to open the system tray icon on or off? Right-click on the taskbar and click Properties,Click the Customomize button,Turn system icon on or off,select vomume and wifi.
---- Thank you for SR feedback!
[1KRAMOS3.8.6-English]
1. microsoft Ramdisk dirver mode (including RPIO, RPCP, RPWimboot under BIOS / UEFI), WIN8 and 10 systems automatically add startisback (in the All1 module) to solve the problem of left-click and right-click on the start menu, if installed Startisback failed, please manually install it in the original system by yourself, and then start production. The batch process will determine whether the original system C:\Program Files (x86)\StartIsBack directory exists. If it exists, do not copy StartIsBack. The purpose is to not overwrite the original system's StartIsBack and ensure that the original system's StartIsBack configuration is valid. I recommend that you install StartIsBack in the original system and configure it yourself. 1KRAMOS3.8.6 does not ensure the reliability of offline installation of StartIsBack. ---- by liuzhaoyzz
2. microsoft Ramdisk dirver mode (including RPIO, RPCP, RPWimboot, etc. under BIOS / UEFI). Win8 and 10 systems are added with the winxshell (by slore) to fix the problem of wifi and volume in the system tray area.The batch will copy WinXShell to C:\Program Files\, double-click C:\Program Files\WinXShell\wifi_volume.reg to join to the startup group, the registry location is HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run Regardless of whether it is 32-bit or 64-bit Windows, the registry calls 32-bit WinXShell_x86.exe to fix the wifi and volume in the tray area. You can also double-click C:\Program Files\WinXShell\UI_WIFI_Volume.bat manually. To start the WINxshell UI_WIFI and UI_Volume modules (32-bit / 64-bit adaptive), after the UI_WIFI is turned on, click 3 pixels in the lower left corner to click to exit, UI_Volume can kill the winxshell process. ---- Thanks slore!
[1KRAMOS3.8.5-English]
1. Modify the startup image file size. The original default is 512MB. Now set to 1024MB. Keep a certain amount of margin to avoid oversized files causing startup and production failure. The modified files include 0.cmd, rc.cmd, backup.cmd.
1KRAMOS3.8.3-English
1. Check the input disk space of the input drive. If the input drive letter is equal to the drive letter of the batch, set the required disk space equal to 3 times the used space of the C drive (fool. ramos.sna+compact.wim+1.vdf+vdf=1x+0.6x+1+0.6x=2.2x+1, or local double mirror ramos.sna+1.vdf+vdf=1x+1+1x=2x+1, local singular single image ramos.sna +vdf+vdf=1x+1x+1x=3x, take the maximum value of 3x); if the input drive letter is not equal to the drive letter of the batch, set the required disk space equal to 2 times the used space of the C drive (because For a fully mirrored vdf, you need to copy and paste to erase the file fragment. To avoid that you can't complete it (snapshot prompts Some error occurred-exitcode 1) at the end.
2. If the partition where the vdf is entered is not MBR partition, a warning prompt is given. For the RAMOS scheme started by grub4dos, if the partition where vdf is located is a GPT partition, vdf may be placed in the sector behind the disk, Vdf may not be found. It will appear in my computer that vdf exists, but when it boots, find -- Set-root xxxx.vdf prompts "File not found". If this happens, you can use the Aomei partition tool to change the partition size under PE. For the mechanical hard disk, make sure that the disk partition where vdf is located is located in front. The new motherboard should be able to access less than 2TB, it is no problem within 137GB in front of the hard disk generally, which depending on the motherboard's ability to recognize the disk in real mode; for SSD Hard disk, because the SSD hard disk has a logic conversion circuit and a dynamic wear leveling algorithm, even if a small partition is divided, the data may still be placed anywhere in the memory chip, there is no front sector like a mechanical hard disk, it is also to see The motherboard's ability to recognize in real mode.
Note: Regardless of the operating system, it is recommended that the original system do not have hidden partitions that affect booting. For example, some computer boot partitions (partitions containing ntldr/bootmgr) are hidden, and the operating system is installed in another partition. It is suggest that the partition is merged with the partition where the operating system is located, activation the partition, and assign the drive letter. Otherwise, there may be a problem to write the boot of the RAMOS; in addition, the vdf is placed in the primary partition as much as possible, for the logical partition grub4dos placed in the back may not be found.
3. Synchronize the bootmode applet to determine if the partition is an MBR partition. The principle and procedure of BootMode.exe can be found at http://bbs.wuyou.net/forum.php?m ... 12368&extra=&page=1 ----Thank you for liuzhaoyzz!
4. Split the snapshot into 32-bit and 64-bit versions, and automatically call the corresponding program according to the number of operating system bits, which is more stable. Snapshot64.exe uses the latest version 1.46.0.18214, only 410KB, the volume increase is small.
5. Determine whether the current system is a 32-bit or 64-bit system and use a more stable code.
6, for the NT6 or higher operating system, determine whether bcdedit can run normally, if it can not run normally, give the prompt "Please find the reason, such as the boot partition is not mounted, the BIOS boot partition is not the active partition or lack of disk drive!", and Exit 1kramos; if it can run normally, start to run.
7. active the RAM disk partition of the RAMOS to ensure that bcdedit can run when the BIOS starts.
8. It is recommended to restart the computer before prompting the production on the interface to ensure that the driver and update take effect!
1KRAMOS3.8.2-English
1, grldr uses the latest version of grub4dos-0.4.6a-2019-03-25, supports file simulation with 32 fragments, support for hot backup better, if prompted after the hot backup Error 60: file for drive emulation must be In one contiguous disk area, use wincontig to manually sort the vdf to eliminate the fragment, or copy and paste the vdf in the original point, delete the original, and rename the new name to the original name. The hot backup program does not elimination fragment, because there is no problem under normal circumstances. Copy and paste renaming is just a waste of time.
2, modify the virtual memory settings in the RPIO, RPCP mode, do not modify the virtual memory settings of the original system, only modify the virtual memory settings in RAMOS to ensure that the primo memory disk in the original system will not be on the memory disk because the virtual memory file is Occupied and cannot be deleted. After the version is updated, the primo memory disk can be deleted directly.
3. The recommended prompt value for the 64-bit ramdisk boot image in the RPIO and RPCP schemes is 1600MB. In case the boot image is too small, the production fails. It is expected that the master can streamline the RPIO and RPCP boot image lists.
1KRAMOS3.8.1-English
1, give up copy / B grldr + ramos.lst RAMOS import menu scheme, because grldr need to use winhex violent modification, empty the menu behind, if encounter grldr in some cases, update the grldr in the batch program is too much trouble, so the grubmenu import scheme is used instead of the original scheme. In the new version, to update the grldr in the batch program, just download grldr from http://grub4dos.chenall.net/ and copy it to a key. Cover grldr.
Regarding the file grldr0.46a, the original grldr uses winhex to find the uppercase GRLDR (in "No GRLDR ...", the modification must be capitalized, the modified address is 3F3 and 5E3), and use winhex to modify the first two place of GRLDR to SXLDR, and at the same time emptied its built-in menu, mainly used for NTLDR boot, you can see this post: grub4dos-0.4.6a-2017-12-23 how to guide the change after the name grldr? http://wuyou.net /forum.php?mod=viewthread&tid=404637&extra=&page=1.
2. Update the cboot4 subroutine and the hot backup program rc.cmd, and extract the \windows\inf, windows\system32\drivers, catroot, and CodeIntegrity directories into the boot image to ensure that the driver takes effect and the hot backup is complete. These files are not large.
3, Add the Primo drive RAMOS local single mirror mode in the BIOS boot advanced mode [complete single image, no dynamic allocation, need large memory, make faster], to solve the problem that Windows Server 2019 vdf dual mirror can not be started, vdf double Mirror mode will restart repeatedly when Windows Server 2019 starts. It may be because the boot image lacks critical startup files, but the extraction of boot files requires knowledge of the underlying operating system. The extraction of boot image files is tantamount to finding a needle in a haystack. so I add by a single mirror scheme, note that the mode requires the original C disk total size (not used space!) is smaller than the memory, and the available memory is large enough to create a primo memory disk, pay attention to the memory disk allocation The larger the start, the slower the startup, because more full mirror data needs to be loaded into memory. The speed of boot depends on the size of vdf and the reading speed of the storage medium where vdf is located. ----Thank Eternal
4. Adjust the position of the cmd window so that it is on the upper side of the screen.
1KRAMOS3.8.0-English
1, according to Amtfo030128, chenyingkeng, buyi and other feedback, the rich mode failed to start, the reason may be caused by the boot image is too large, from this version, fool mode, local mode, WIMBOOT memory and hard disk mode, distant mode boot image is positive Replacing the reverse list with the copy list, thereby reducing the size of the boot image to less than 300MB (the actual setting of the boot image is 512MB), and also reducing the production time. The boot image list is mainly from 2012wuzhong. This version has changed a lot and requires extensive testing. ----Thanks to 2012wuzhong!
2, the rich mode RAMOS_C disk size is adjusted to the memory size, pay attention to the rich mode requires the physical hard disk or VHD disk total size must be less than the total amount of physical memory! This is because Drive snapshot currently only supports hot backup from small partition to large partition; when cloning from large partition to small partition, the total capacity of small partition must be larger than a certain storage space, and strange problems may occur. For example, the system is installed in the VHD, the total size of the VHD is 30GB (the used space is 15GB), the physical memory is 32GB, you can use the local mode, and also pay attention to the available space of the hard disk is large enough, such as 15* 3=45GB or more is available, after the RAMOS_C disk is 32GB. Special attention must be made to run as a administrator! Be sure to run as a administrator privilege! Be sure to run as a administrator privilege!Be sure to run as a administrator privilege! Also for 64-bit systems, don't run the batch from a third-party 32-bit file browser, because 32-bit file browsers don't have direct access to certain windows and registry files, recommended from Windows Explorer. The read and write permissions of some files go beyond the ability of Nsudo. ---- Thanks for the feedback of real456!
3,(1) improve RPIO, RPCP virtual memory scheme to avoid shutdown blue screen problem. After running the RPIO and RPCP schemes, the primo memory disk of the original system must be deleted before the virtual memory of the primo memory disk is closed. My computer→right-click Properties→Advanced System Settings→Advanced Tab→Settings→Advanced→Select No Pagination File → set and confirm, then restart normally, you can delete the memory disk after rebooting, it is best to restart once after deletion, otherwise it may affect other mode production. (2)gives the recommended range of Microsoft Ramdisk memory disk, and can manually enter the value, 32-bit general 400-900MB, 64-bit general 800-3200MB. (3)Improve the list of boot images under RPIO and RP COMPACT schemes (including MBR and UEFI), abandon the original win.ini and win1.ini schemes, use win2.ini scheme to reduce the capture range, and avoid starting mirrors that are too large to start. Problem; create a soft link to the first level directory in addition to the aaa.txt list directory in the boot image. (4)Because different computers have various files in the system32, syswow64, and fonts directories, so the bbb.txt file link list is discarded, and the batch code is directly used for online real-time extraction instead, and if the file exists, it is automatically skipped. (5)Adjust the list of deleted boot images in ccc.txt to enhance stability. However, these Ramdisk-based solutions under UEFI still have some remaining problems to be solved under the WIN8/10 start menu. This version has changed a lot and requires extensive testing. ----by liuzhaoyzz!
4. Update the hot backup program rc.cmd to ensure that the registry settings take effect.
5, in addition to using the powercfg -h off command, also try to use the registry to shut down hibernation, to avoid Hiberfil.sys brought into RAMOS. ----Thank yamingw
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power]
"HibernateEnabled"=dword:00000000
6, Wimlib uses the latest version of 1.13.0 from https://wimlib.net/, which officially said that when the [ExclusionList] field has a matching wildcard file, [ExclusionException] forces the absolute path to be invalid.
7, increase the delay in the construction of the disk, delete the disk, to ensure that the production is not stable blue screen (the official follow-up version also corrected this bug).
8. Delete the statement that creates PCBackup.cmd on the desktop.
9. The recommended production mode is given under each interface. The recommended mode is no longer simply to look at the speed measurement index, but more importantly, compatibility and stability are not considered. The Direct-IO mode is no longer recommended, because this mode is officially introduced by Romex. Not as stable as the SCSI mode, but also the instability caused by soft links.
10.fixed the bug of get GUID in English version.
11.fixed blocked error when input primo disk space in RPIO,RPCP mode.
1KRAMOS3.7.6-English
1.Microsoft Ramdisk driver + Primo [WIMBOOT, WIM put memory disk] mode supports UEFI-WIN7 8 10, the theory come from 2012wuzhong's tutorial "based on p62 uefi ramdisk+scsi-wimboot production - RAMOS" http://bbs.wuyou .net/forum.php?mod=viewthread&tid=411938&extra=
According to the tutorial of 2012wuzhong, three nls (C_437.NLS/l_intl.nls/locale.nls) files and three directories (\Windows\System32\catroot, \Windows\System32) have been added to the WimBootCompress.ini[PrepopulateList] exclusion list. \CodeIntegrity, \Windows\System32\drivers), restart and shut down normally without blue screen. Note that the WINF8.1 and WIN10 can't open the start menu by left click. It is recommended to install the software such as Startisback in the original system to solve the start menu problem. If your memory is too small, the virtual memory can be turned off in the original system C drive. And set the hard disk with the larger remaining space to "system managed size" to eliminate the "page configuration problem when starting the computer" dialog box.
Legacy issues: the tray area network and sharing center in the lower right corner, the left button of the small speaker can not be opened. ----Thanks to Tiger 2012wuzhong!
1KRAMOS3.7.5-English
1. Fixed WimBootCompress.ini exclusion list windows directory writing typo; fixed 0.CMD wofadk driver group "system Bus Extender" writing error. You don't need to re-do RAMOS if it run well. ----by 2010hook
1KRAMOS3.7.4-English
1. Added UEFI boot, Ramdisk+Primo-SCSI-COMPACT compression mode, support WIN7 8 10, use img as a small boot image to put Ramdisk memory disk, other files are put into primo memory disk by soft link. The files in the ramdisk are compressed with COMPACT. There are problems to be solved: In this mode, the left button of the WIN10 start menu is invalid, and the shutdown will be blue screen. It may be related to the adoption of the soft link. The Explorer.exe has been placed on the Ramdisk disk, but can't fix the error. WIN7 does not have this problem. For starting img small image + Ramdisk + primo IO mode, only one exclusion list of win.ini is used. The [ExclusionList] field in the list will be excluded from Ramdisk, and the file under the [ExclusionException] field will be forced to remain in Ramdisk. In img, this win.ini list requires everyone to do more work to determine more accurately, the current Ramdisk driver file has 400MB-700MB. The img memory occupied by UEFI is too large, and the Ramdisk driver and soft link will cause the WIN10 start menu to be clicked invalid, expecting to improve or completely discard Ramdisk.
2.bcdedit on some WIN7 system will prompt "can not open the boot configuration data storage. Can not find the requested system device", fixed the bug by bcdeditX86 in WIN8. After bcdeditX86 runs once, bcdedit generally works normally.
3. Change the RAMOS boot entry of the Microsoft Ramdisk+Primo driver from the original boot-img-date time to the R-Primo-RAMOS-datetime format to ensure the startup is the same in the boot bootnames in Bootice.
4, Microsoft Ramdisk driver + Primo [WIMBOOT, WIM in hard disk] mode supports WIN7 8 10, add hints in the interface, but he is a semi-memory solution.
5, pay attention to the RAM+primo boot startup item of Microsoft Ramdisk+Primo driver. If you use Bootice to edit and save, you must find the corresponding Device objects item in advanced editing mode, delete SdiDevice and SdiPath, otherwise it will boot fail. ---- by liuzhaoyzz
1KRAMOS3.7.3-English
1、BIOS mode, the Primo driver NTFS compression mode is added in advanced mode 7. For WIN7 compression ratio is about 64%, this mode uses two images, which occupies almost the same memory as the rich mode, but the RAMOS C disk is NTFS compressed. Can free up a certain space of the C disk for installing software, compatibility stability is good, can solve the problem of VB6 and other software open abnormalities, because it cost large memory, users with small memory are not recommended to use this mode.——by liuzhaoyzz
2、Add one key RAMOS English,fixed the bug "cannot find the disk #0"----by liuzhaoyzz
|
评分
-
查看全部评分
|
[复制链接]
IP卡
狗仔卡
发表于 2018-10-4 18:23:49
收藏
支持
反对
提升卡
沉默卡
喧嚣卡
变色卡
千斤顶
显身卡
楼主
发表于 2018-10-4 18:52:16
