Firadisk virtual disk enumerator скачать драйвер для windows 7

Меню Проекта

Главная страница Руководство по Grub4Dos Руководство по Syslinux Каталог статей Склад Форум GfxMenu Книга Жалоб и Предложений Cкачать?! Информация о Проекте Обратная связь

Мнение Общественности

Сколько у вас Флешек? 1. 2 две 2. 3 три 3. 1 одна 4. 4 четыре 5. 5 пять 6. больше.. 7. 6 шесть 8. 8 восемь 9. 7 семь Всего ответов: 4545

Статистика

Страница 1 из 5

blohhh, дык вроде как уже более чем полгода гуляет конфликер))) и его клоны. Я его уже руками чистить без особых проблем научился за это время.

А по теме, вот откорректированный слегка файлик (зачем это смотрите на msfn и в этой теме выше)

Если будете тестить в VMWare, то не забывайте про волшебную кнопку F6 и подгрузку драйверов SCSI в комплекте с Firadisk. Тоже самое касается вариантов установки с USB на USB (для этого тоже нужно жать F6 и подгружать драйвера. )

Добавлено (02.10.2009, 02:42)
———————————————
В общем-то могу сказать, что установка с частично загруженного в память исошника работает нормально
Что и как было сделано:
1. Был взят оригинальный VLK-образ с WinXPSP3 и распакован в папку d:5WinXp
2. Из этого же диска выдран загрузочный сектор, назван как bootsect.bin и положен в папочку d:5WinXp
3. Выкачал драйверпаки с http://driverpacks.net/ и интегрированны в папку d:5WinXp по методу №2 (качал на проц, рейды, сеть и че-то еще. тяжеловесные типа звука и видео не интегрировал )
4. Собираем исошник, такой строкой (mkisofs.exe и нужные dll, естественно должны быть):

Источник

FiraDisk (latest = 0.0.1.30)

FiraDisk
File/ RAM Disk driver for Windows.
From discussion in Shao’s topic GRUB4DOS RAM Disk Recognized by RAMDISK.SYS, I try making a Windows driver to read GRUB4DOS’ drive map table and use GRUB4DOS RAM drives in Windows. This driver is the result. It emulates SCSI adapter and disk. It can use RAM disk loaded by GRUB4DOS in Windows.
Shao’s driver WinVBlock can also use GRUB4DOS’s RAM drives. You can visit his thread for more detail.

This driver is not suitable for people who are not familiar with making and manipulating disk image or don’t know how to use GRUB4DOS.
It may take a long time to study about them depending on each person.

Windows PEs created from Winbuilder are useful for data recovery and manipulation of harddisk partition.
They are normally run from CD-ROM. If you don’t want to burn CD, or the computer you want to run it on don’t have CD-ROM drive, another option is run from USB drive.

GRUB4DOS has ability to load disk image to RAM and create RAM drive for use in DOS, Windows 98. You can boot DOS, Windows 98 in RAM.
Newer Windows based on Windows NT cannot use GRUB4DOS RAM drive unless you have driver for it.
With FiraDisk driver you can use GRUB4DOS RAM drive in Windows XP-7. It can be used to boot Windows.

If you have FiraDisk integrated in PE ISO. It is possible to use GRUB4DOS to load PE from ISO file into RAM and run PE from RAM.
When you run Windows from RAM. You can use your recovery tools, antivirus, partition managers to modify your harddisk. You can also delete/rename some folders (Document and Settings, Program Files, Windows) and reinstall Windows in old NTFS partition without deleting your data files and don’t get old and new files mixed.
You can store multiple ISO files on the same drive and choose it in GRUB4DOS at boot time.

Platform:
Can run in
— Windows XP 32-bit
— Windows Server 2003 32-bit
— Windows 7 32-bit
— Windows 7 64-bit (Test Mode)

Test-signed 64-bit driver is included. If you want to test it in Windows Vista or Windows 7 64-bit, you must enable TESTSIGNING Boot Configuration Option before you install this driver.
If you don’t want to be warned about unknown publisher, you may install my self-signed test-signing root certificate before you install this driver. TestSignRootCA.reg ( 4.78K )

Planned features in future versions:
— Add/remove drives from CLI or GUI.

file= path : File read/write.
vmem= path : Memory mapped file.
vmem without path : Allocate from virtual memory (RAM+pagefile).

offset= number
size= number
heads= number
sectors-per-track= number
ro : read-only
boot : indicate that the virtual drive is required for booting Windows.

method 2. Use devcon utility if you have devcon.exe.
devcon install firadisk.inf rootfiradisk

method 3. (v0.0.1.6) Right click firadisk.inf, select Install. FiraDisk will start at next boot time. When Windows prompt you to install driver for the new firadisk device, just follow the instruction on screen.

After installation you can see ONE «Firadisk Virtual Disk Enumerator» device node in Device Manager.
If you install multiple times and have more than one «Firadisk Virtual Disk Enumerator» device, right-click and select Uninstall.

Test FiraDisk with GRUB4DOS mem drive (non-boot drive)

Test FiraDisk with GRUB4DOS mem drive as boot drive

How to create/mount raw disk image with FiraDisk 0.0.1.12 (updated 2009-09-30)
Not very convenient though.

How to clone Windows XP by copying files to different disk (or image)

Wow, very impressive.

Just booted xp from a ramdisk image at 2,3Gb, completely diskless!!

Next thing is to figure out how to make PE boot from it. Do you know what is required entries in txtsetup.sif?

Even better, it now also works in PE-mode.

I just booted moa from a 550 Mb image. I’ll be back with the details when sorted out.

PE-mode requires adding this to txtsetup.sif;

and applying this registry patch to setupreg.hiv;

Seriously, I believe one company just lost their business.

Seriously, I believe one company just lost their business.

— Make a raw disk image with makedsk.exe (makedsk.exe 640.dsk 649797120).

Joakim, what tool do you use now for initial creation of raw disk image?

I would like to say thank you to karyonix for spending time and effort to write the driver, starting the thread & taking the time to write a good How to and make driver available for free.

Please can Joakim or karyonix confirm image file must be contigous?

Before wiping my system partition and recreate a new contig image file (solved the issue), i had error:
Grub loads from boot.ini on c: drive (which is ntfs), but then fails to load hdd.img.
Error 15, File not found.

To mount the raw image and successfull creation of the partition and disk signature, i used
virtual storage driver, from Microsoft
e.g.,

640.dsk
format : /FS:NTFS /V:SYSTEM /C /Q /A:512 /Y
vstorcontrol remove \.PhysicalDrive X

No need to use the tool from one company.

Firadisk driver installation instruction for Windows XP

Copied firadisk.inf to

inf
Copied firadisk.sys to

system32drivers
Injected driver to my offline Windows install loaded SYSTEM hive as SYSTEM.SAV, e.g.,
may not work for anybody. Please notice i have an other SCSI device:
Microsoft iSCSI Initiator
HKEY_LOCAL_MACHINESYSTEM.SAVControlSet001EnumRootSCSIADAPTER 0000
FiraDisk Virtual Disk Enumerator
HKEY_LOCAL_MACHINESYSTEM.SAVControlSet001EnumRootSCSIADAPTER 0001

Joakim, what tool do you use now for initial creation of raw disk image?

I do it manually with the dsfok tools and vdk with the help of a spreadsheet; http://www.mediafire. _calculator.xls
But the best tool is probably jaclaz’s mbrbatch tool. I have a collection of 5 ready disk images that was uploaded earlier; http://www.mediafire. eady_images.zip

Please can Joakim or karyonix confirm image file must be contigous?

To mount the raw image and successfull creation of the partition and disk signature, i used
virtual storage driver, from Microsoft
e.g.,
No need to use the tool from one company.

Well, good to hear about other tools to use too. It’s really just about being comfortable with a way that works.

Note, gzipping the images is recommended for several reasons.

may not work for anybody. Please notice i have an other SCSI device:
Microsoft iSCSI Initiator

I don’t use such, so I have no idea. Someone else must supply working instructions for use with such setups. Did it work for you or not?

I do it manually with the dsfok tools and vdk with the help of a spreadsheet; http://www.mediafire. _calculator.xls
But the best tool is probably jaclaz’s mbrbatch tool. I have a collection of 5 ready disk images that was uploaded earlier; http://www.mediafire. eady_images.zip

Nice, i will download Ready_images.zip

OK, issue i had was may be something else (typo error?)

Well, good to hear about other tools to use too. It’s really just about being comfortable with a way that works.

No GUI but very convenient for me.

Note, gzipping the images is recommended for several reasons.

Will try to GZip my hdd.img, now that you answered my question about contigous file.

I don’t use such, so I have no idea. Someone else must supply working instructions for use with such setups. Did it work for you or not?

It was not a question but an alternative to both methods suggested by karyonix.
If someone try to past my reg file and inject it to offline SYSTEM hive, he won’t get the attended result because i have Microsoft iSCSI Initiator installed on my Windows XP. Some edit to the reg would be necessary (replace all 0001 by 0000)

grub4dos question: the sample menu.lst listed below is from one company and i changed the titles to be more explicit. i have not tested it and would like to have some advices from advanced users.
hdd.img Partition 1 is a copy of Partition1 Windows XP install on internal drive (4 primary partitions).
Can i use this settings in menu.lst to hide Partition1 on the internal drive (disk signature CEF9D879) when i boot the Partition1 from hdd.img (disk signature 1D01D3CE)

Joakim, i want to achieve something similar as the tool you have written for VMware users: rawdisk_cmd

My menu.lst looks like this;

The 2400.gz is a 2,2 Gb (2 393 556 480 byte) large disk image which is gzipped to 696 Mb and placed inside iso. It was running fine for almost 2 hours until I shut it down.

Note, running it in PE-mode will not require disk signature to be present in registry.

v0.0.1.4
— Support multiple virtual drive.
— Support CD-ROM ISO loaded with GRUB4DOS.
— No floppy drive emulation. Floppy disk image mapped to (fd x) will appear to be removable disk.

example menu.lst entry

Do you know if that means it can handle unmanaged memory, like above the 3,2Gb rough limit.

@karyonix
I get with FiraDisk v0.0.1.4:

This get a nice BSOD 0x7b
I imagíne, in future you map real floppy images (e.g. 2880 sectors) to a floppy drive a:
One target: XP installation from a FiraDisk drive. And load F6 drivers from a virtual floppy a:

Continue the excellent work. Take your time.

I’ve found one of my mistakes.

Thanks a LOT for your driver.

Can you clarify if the latest version supports CD iso booting or if we should wait for the next version? Thanks.

Please try this one.
http://www.mediafire. ver-0.0.1.6.zip
— Bug fix: It should not wrongly see CD-ROM drive 0xFF as RAM drive anymore.
— Add: boot.ini option for file disk. It is not bootable.
example:
/firadisk= disk, file= c:hdd1.img
/firadisk= disk, file= c:hdd3.img, size= 32901120
— If there is no registry entry for firadisk enumerator device (such as EnumRootSCSIADAPTERxxxx) when firadisk service start at boot time, it will create a new firadisk enumerator device. Its registry key will be EnumRootfiradisk000.

EDIT: I forgot to write the keyword «file=».

I would like to update Windows installation offline with this new version.

I noticed a new setting in firadisk.inf

[MfaKaryonix.ntx86]
%FiraDiskDevice%=FiraDiskDevice, rootfiradisk, detectedfiradisk

— If there is no registry entry for firadisk enumerator device (such as EnumRootSCSIADAPTERxxxx) when firadisk service start at boot time, it will create a new firadisk enumerator device. Its registry key will be EnumRootfiradisk000.

Using method 2 for installation to create a snapshot of driver install for later injection to offline registry hive
it’s not required to run this command

i searched with google to find infos about «detected» setting in registry keys but didn’t find valuable information.

Will wait for your instructions before injecting new keys value and data to my system hive.

method 3: Right-click the new firadisk.inf and select Install. And reboot.

If you install with method 3, only firadisk service is installed. No device key will be created until reboot. While booting, firadisk reports a new device. Windows assigns compatible IDs «detected. » to the new device (as described here). The registry key created by Windows for firadisk device is EnumRootfiradisk000.

It seems it does not matter whether device registry key is EnumRootSCSIADAPTER000 or EnumRootfiradisk000. FiraDisk work the same way.

In INF, hardware ID «rootfiradisk» and compatible ID «detectedfiradisk» is for installation and upgrading driver associated with firadisk device.

Just installed the new version only by replacing files:
binary %SystemRoot%system32driversfiradisk.sys
inf file %SystemRoot%inffiradisk.inf

and changed version info with offline injection of new data values

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINESYSTEM.SAVControlSet001ControlClass<4D36E97B-E325-11CE-BFC1-08002BE10318>001]
«InfPath»=»firadisk.inf»
«InfSection»=»FiraDiskDevice»
«InfSectionExt»=».NTx86″
«ProviderName»=»Karyonix»
«DriverDateData»=hex:00,80,61,7c,72,27,ca,01
«DriverDate»=»8-28-2009»
«DriverVersion»=»0.0.1.6»
«MatchingDeviceId»=»root\firadisk»
«DriverDesc»=»FiraDisk Virtual Disk Enumerator»

Created a new 64 Mb hdd1.img, edited boot.ini (inside main 640 Mb hdd.img containing Windows XP install) and boot successfully.

now i have 2 new disks drives listed in device manager. FriendlyName are «File Disk» and «RAM Disk» instead of single FriendlyName «Virtual Disk» with firadisk 0.0.1.0

A suggestion could you use ARCpath for setting the File disk

the bad news: new version crashed my Windows install when i tried to install another commercial Superspeed RamDisk Secure 8.0.4 (digitally signed driver that pass Microsoft WHQL tests) and very stable (never crashed before with this driver) and now hdd.img image content is messed up.

[EDIT]
now restored from backup. back to firadisk 0.0.1.0

What’s a good way to grab an image of a partition with track0?
For this test I ran dsfo on the whole drive and used ctrl-c, but I’d imagine there’s a cleaner way.

What’s a good way to grab an image of a partition with track0?
For this test I ran dsfo on the whole drive and used ctrl-c, but I’d imagine there’s a cleaner way.

I like DD for Windows by John Newbigin. A partition can be gotten withwhere XXX is the partition’s size, in 512-byte sectors. If you have the good fortune that there is nothing between track 0 and this partition, then you can simply grab the first track withwhere X corresponds to the physical drive’s number (you can find this out with TinyHexer, WinObj, others) and YYY‘s most common value is 63 sectors-per-track. You’d have to verify these parameters, perhaps by using BeebleBroxNT or some other utility. Then you could concatenate track 0 with your partition image OR

If you have the good fortune (as before) to simply have track 0, then partition, simply add the count for sectors-per-track for track 0 with the sectors-per-your-partition. Then you couldwhere YYY would be this calculated sum, such as 63 + partition_sector_count.

I see that the size of the CD Rom drive in Windows is 515MB, nothing is readable within the cd. The actual size of the cd is 128 MB. Name in Device Manager is RAM CD-ROM Drive. In Disk Management, shown as 515 MB. In properties, file system is shown as RAW with used and free space as 0 bytes.

Something doesn’t seem right. How is the CD iso mapping supposed to look within windows?

What’s a good way to grab an image of a partition with track0?
For this test I ran dsfo on the whole drive and used ctrl-c, but I’d imagine there’s a cleaner way.

If it’s the first partition on a hard disk (and that it has drive letter F::

Three step process:
1. dsfo \.Physicaldrive N 0 32256 C:myhidden.img N 0 526450176 C:myfull.img

I see that the size of the CD Rom drive in Windows is 515MB, nothing is readable within the cd. The actual size of the cd is 128 MB. Name in Device Manager is RAM CD-ROM Drive. In Disk Management, shown as 515 MB. In properties, file system is shown as RAW with used and free space as 0 bytes.

Something doesn’t seem right. How is the CD iso mapping supposed to look within windows?

It is supposed to be the same size as ISO (128 MB).
While I corrected errornous detection of CD 0xFF as RAM drive, I made another mistake in FiraDisk 0.0.1.6 causing it to calculate address and size of RAM CD-ROM incorrectly.

In previous 3-4 days, after fixing the mentioned bug, I changed some data structure of FiraDisk to better support creating drive from /firadisk boot.ini option. But when I tested it, Disk Management did not recognize modified FiraDisk’s drive anymore, including RAM disk. I cannot find what was wrong, so I think I had to roll back to 0.0.1.6 and work from there again.
I will release a new version that have RAM CD-ROM bug fixed today even though /firadisk boot.ini option is still not working very well now.
—

To avoid GRUB4DOS’ warning, use whole disk image size that is multiple of cylinder size (default 255*63*512 = 8225280 bytes). However, if disk image is uninitialized (no MBR code, no partition) or have MBR but does not have any formatted partition, GRUB4DOS will think it is partition image and add 1 track automatically (usually 63 secters) increasing disk size, and result in warning message.

However, if disk image is uninitialized (no MBR code, no partition) or have MBR but does not have any formatted partition, GRUB4DOS will think it is partition image and add 1 track automatically (usually 63 secters) increasing disk size, and result in warning message.

or have MBR but does not have any formatted partition

or have MBR but does not have any formatted valid partition entry in it

Источник

Adblock
detector