> For instance, I am currently running at least 6 browser engine instances as I type this, probably more than that, and I just am not experiencing a meaningful performance hit As a matter of fact, if you're a programmer, your hardware is probably significantly better than the average computer user. Don't assume that everyone else is in the same situation as you. ![]() I can think of a dozen situations where 140 MB is a problem. Or, if you have a large, but slow, HDD in an older computer (or worse - a small and slow SSD in a netbook), then reading that 140 MB installer (or the potentially-even-larger installed program) is going to be far worse than a 5 MB one. Or if you're building a system recovery image. If you're on a 32 GB SSD (like I was just a few years ago), 140 MB for a highly specialized tool is a huge amount. If you have a 16k connection from Ethiopia, then 140 MB takes almost 20 hours to download (5 MB is 43 minutes, 630 KB is 5 and a half minutes). ![]() If you live in Africa and have a connection like Ben Kuhn, 2.6 mbps, then downloading that 140 MB installer will take over 7 minutes, while a 5 MB installer will take 15 seconds, and Windirstat's 630 KB will take about 2 seconds. If I'm on the go, or my home internet is down (like it is now), that 140 MB is a seventh of my internet for the entire month. > Honestly, is 140 MB really a problem anymore? With the full fileset of the live Linux distribution copied to the bootable Syslinux'ed FAT32 USB drive, change the name of the isolinux folder to syslinux and inside your new syslinux folder, change the name of isolinux.cfg to syslinux.cfg.Ī good live distribution will then boot from a Syslinux'ed USB FAT32 partition using a syslinux folder, instead of from a DVD using an isolinux folder. C32 files in the syslinux folder need to be the same version that you SYSLINUX'ed the partition bootsector with. Which then searches for the syslinux folder and a syslinux.cfg file inside. When you SYSLINUX the target FAT32 partition using either Windows or Linux, that writes a Syslinux bootsector to the partition (also writes ldlinux.sys & ldlinux.c32 files) which seeks & loads ldlinux.sys (and ldlinux.c32). When you format the FAT32 partition using DOS, or execute SYS.COM on the partition, that would write a DOS bootsector to the partition which seeks & loads IO.SYS. When you format the FAT32 partition using Windows 10, or execute BOOTSECT.EXE /nt60 on the partition, it writes an NT6 bootsector to the partition which seeks & loads BOOTMGR.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |