9 replies to this topic

[Brito]

Hi,

There is also a discussion topic open on 911cd.net where more users are also discussing ImDisk applied on bartPE: http://www.911cd.net...showtopic=19711

[pscEx]

Hi,

There is also a discussion topic open on 911cd.net where more users are also discussing ImDisk applied on bartPE: http://www.911cd.net...dex.php?t=19711

The link leads me to the forum's root.

Peter

[Brito]

Corrected the typo, should have been "showtopic=" instead of just "t="

[bilou_gateux]

Imdisk as a RAMdisk !!, Plus a plugin from paraglider

Thanks for joining all posts, but I think the title should still be edited or split the plugin post - paraglider is the one who proposed a plugin and deserves the credits for his work - not myself..

[TheHive]

I Posted some test results on that thread so if you have some time check it out Olof.

[paraglider]

I am noticing some weird effects when I create a ram drive from the command line. If I try to format it as NTFS sometimes it will fail saying it could not write the control information. If I however create a drive of the same size from the gui then the command line NTFS format always works.

[Olof Lagerkvist]

I am noticing some weird effects when I create a ram drive from the command line. If I try to format it as NTFS sometimes it will fail saying it could not write the control information. If I however create a drive of the same size from the gui then the command line NTFS format always works.

Interesting, have never noticed that... I would very much like to know more about it if you have something reproduceable, also extact OS version, Service Pack level, amount of RAM etc would be useful.

[was_jaclaz]

I am noticing some weird effects when I create a ram drive from the command line. If I try to format it as NTFS sometimes it will fail saying it could not write the control information. If I however create a drive of the same size from the gui then the command line NTFS format always works.

Could it be some kind of "timing" problem?

Maybe if you try with very small images it works and with rather big ones it doesn't or viceversa?

jaclaz

[paraglider]

OS was PE based off XP + SP2 + latest hotfixes. Created ram drive was 50mb. Total ram size was 2gb so its not an amount of available ram issue. When the ntfs format fails I can format as FAT without a problem. Here is the error:

[Olof Lagerkvist]

OS was PE based off XP + SP2 + latest hotfixes. Created ram drive was 50mb. Total ram size was 2gb so its not an amount of available ram issue. When the ntfs format fails I can format as FAT without a problem. Here is the error: ...

Okay, I see. I found out that this problem only occures when you create virtual disks with sizes that are not multiples of 512 bytes. Because you specify -s 50mb the size will be 50 * 1000 * 1000 bytes and that is not a multiple of 512 bytes. This messed up the auto-selection of virtual geometry in the driver so it selected 1 bytes/sector as sector size and that is not compatible with NTFS. You can either add -S 512 to your command line to manually specify a sector size of 512 bytes or change the size to for example -s 50Mb (notice capital 'M') which will translate to 50 * 1024 * 1024 bytes, which is multiple of 512 bytes.

...or download the latest build, I have now changed the auto-selection of geometry so that it always selects 512 bytes as sector size for virtual hd or fd when no sector size is manually specified with the -S parameter.
http://www.ltr-data..../imdiskinst.exe