2/18/2024 0 Comments Windows 7 64 bit virtualbox imageThen you tried B ( for 1 and 1/2 day) and - for whatever reasons - you (partially) failed at it.Ĭonclusion: A is soooo much better than B. So, you tried A (for several months) and - for whatever reasons - you (partially) succeeded at it. always ready for anyone who begs to differ, though. the flattened cosmetics has made it lighter and quicker than win10, at least from a mere user's point of view like mine. To those that say that microsoft has not improved its OSs from win7 onwards, I feel like replying that in fact it has with win10 in many respects, some of which I already mentioned in other posts. As far as I can understand, whatever makes ppl believe win7 is lighter and faster lies in sheer Impressionistic Enlightenment. Like hell, it booted into bsod, and the wim was no smaller than the win10 wims I have. at the end of the experiment, I also wanted wimboot it to see if less space would factor in timewise. there is very very much less to debloat, true, but it is paradoxically not as easy to take out whatever features one does not need as with win10. the transition from post-install first boot to the most analogous configuration possible to win10 was one hell of an adventure with win7 (initial driver injections, incompatibilities, mismatches, system refractoriness to modification, etc.). This was tested after 1 and a half days of getting win7 to the same config as my win10s, not without issues though. win 7 takes more space than and twice as much time as I expected. I was surprised too, despite I have always been a purporter of win10 both in terms of space and in terms of time. 1 and a half day lost - well, nothing is lost in experimenting - at least now we know that, on the same machine, there is an 8-second bootup delay between win10 (14secs) and win7 (22secs). so many ppl say win7 is lighter than win10 so I wanted to scrape a few gbs and secs off the win10 wimboot deployments I mentioned above. This gives you the best possible starting point for building images which will require additional drivers.Sorry to butt in unexpectedly, but I am just after trying out a win7 vhd to compare it with my win10 versions. In the context of a virtual machine therefore, the choice of IDE puts the virtual machine into the "lowest common denominator" of hard disk configurations and does not require any additional hard disk drivers to be present. Most SCSI controller cards included their own bios chip to extend the motherboard bios, and since controller bioses are initialised after the system bios, it allowed them to "hook" the hardware interrupt (Int13) used by the hard disk system and take over the handling of read and write requests. Consequently, all versions of Windows ever released also support IDE natively, as this is the lowest common denominator of hard drives.Ĭonversely, SCSI has always needed additional firmware and software support to work in the PC environment. Of course there have been some enhancements to support the ever increasing size of hard disks, but basically, all IBM compatible machines in the last 25+ years have worked to the "IDE" spec. With the arrival of Serial ATA back in 2003, the ATA interface was retroactively named Parallel ATA, hence we now have SATA and PATA.įrom a BIOS perspective, going right back to the original IBM PC, the way that the bios talks to hard drives has remained virtually unchanged, as the IDE drives mimicked the task file architecture of the original MFM+Controller hard disk setup. So the terms IDE and ATA have been used interchangeably over the years as they are essentially the same thing. As with all good ideas, it was used as the basis of a "standard" known as the AT Attachment or ATA interface. SCSI had been doing this for a while already, but was considered too expensive for standard desktop machines, so IDE was developed by Western Digital to address that market. Prior to that, the older MFM RLL and ESDI disk interfaces relied on an external controller to handle head cylinder and sector addressing, and also to decode the amplified analog signals received from the heads. IDE stands for Integrated Drive Electronics, and was used to describe hard disks with the controller integrated into the drive, rather than being a separate card plugged into the motherboard.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |