![]() ![]() Here now is the other reason that I didn't mention earlier - on occasion as I'm writing code, I'll make a mistake (a bug in the code, who could believe that ). When shuffling all this data around, it can move quite a bit of data, especially through repeated test runs as I'm modifying the program. There's a lot more, but you get the idea. It can reorganize the contents of an ISO image and even allow for the changing of metadata associated with each Windows edition. It can create bootable media, including bootable media with an unlimited number of images. It can automatically convert ESD images into WIM images. It can inject updates, drivers, boot critical drivers into multiple editions of Windows and combine them into a single image, including both x86 and 圆4 editions in the same image if that is what the user wants. My program performs just about every function related to management of Windows images that you can think of. I actually simplified my logic, but here is some more detail. My primary SSD has a 1.6 Petabyte writes rating. What type of development is this where you are thrashing around many GB that frequently? Databases? Even then the rated cycles on a quality SSD are not really an issue anymore.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |