Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About longo213

  1. Yah, but still got to play with Magic ISO. VFD solves that all. Writing my explanation took much longer that all of that
  2. I'm just curious why to use the MagicISO/WinRAR mumbo jumbo when there is much easier way to do it. I did not used floppy drive in any of my machines (PCs and laptops) for almost six years, with USB flash drives and Virtual Flopy Drive (yah VIRTUAL!) and I'm all set. Just download it, unzip, run the file named vfdwin.exe and in the Driver you need to click on the Start button - which will install and start VFD's driver. In Drive0 tab click to Change button, change the drive letter to any available (A: is usual) and hooray - you have unformatted, virtual 1.44" floppy in virtual drive You can also open existing flopy image file (check the Open button), but for this case it's not needed. Then you can run Intel's f6flpy32.exe, format the non-existent drive and let it do it's job. After that you can check the "A:" drive with windows explorer and all the Intel SATA drivers files are there and you can copy them anywhere you wish to. Click to Driver tab on VFD's Control Panel, then on Uninstall button, close... all in 30 seconds, max. Virtual Floppy Drive is an useful piece of (free!) software - you can create, open, change the content of floppy images and then save them into files, which might be useful if you want to use them for bootable CDs, for example.
  3. Would not be better to add those entries into the INF file instead of overwriting some older ones? Would be much more useful, for example if someone wants to include the drivers into his Windows installation with nLite.