[script] ImDisk

I added the new ImDisk.script which can replace the current QSoft RAM drive.

brings as result:

You can see the ntfs compressed HDD.

Peter


EDIT: This caused a new version 029 of explorer script, just for a new Verify condition.

Edited by psc, 04 June 2007 - 12:44 PM.
Additional info

GOOD!

jaclaz

Cool!

I dont know if its possible but is there a way to have imdisk have an autoram resize based on ramsize on PC's. Like a percentage.

I dont know if its possible but is there a way to have imdisk have an autoram resize based on ramsize on PC's. Like a percentage.

If the RAM-disk is created using the command line tool imdisk.exe it is possible to specify the size of the virtual disk as a percentage of currently free physical RAM. Example:

imdisk -a -s 10% -m B: -p "/fs:ntfs /c /q /y"

This will create a RAM-disk B: with the size of 10 per cent of currently free physical RAM and format it with NTFS with compression turned on.

If the RAM-disk is created using the command line tool imdisk.exe it is possible to specify the size of the virtual disk as a percentage of currently free physical RAM. Example:

imdisk -a -s 10% -m B: -p "/fs:ntfs /c /q /y"

This will create a RAM-disk B: with the size of 10 per cent of currently free physical RAM and format it with NTFS with compression turned on.

Thanks, Olof
I'll implement tomorrow in the ImDisk script.

Peter

Great

thanks Peter for the script and Olof for this great utility

A new version is on the nativeEx server.

You now can define the RAM disk size either in megabyte or in percent of the free RAM size.

Peter

Looks simple and very professional!

Had a bit of time to test it. Works well.
It becomes B drive compressed.

Questions:
Can we choose the drive letter or does it default to B drive.
What if you run both the Imdisk script and the Ramdrive script. Who supercedes who?

Once you have Imdisk as the B drive, can we have a way to increase the size of the ImDisk B drive, once your booted into the PE environment.

Can we choose the drive letter or does it default to B drive.

You can edit Fundamentals.script, add and select the RAM drive letter of your choice.

What if you run both the Imdisk script and the Ramdrive script. Who supercedes who?

Thanks for the hint. I'll add a Verify check! New version will be available in some minutes.

Once you have Imdisk as the B drive, can we have a way to increase the size of the ImDisk B drive, once your booted into the PE environment.

There is a command line possibility to INCREASE the RAM drive:
imdisk -e -s <increase size> -m <drive letter>

Peter

EDIT: I delivered a new version of Fundamentals.script, giving the choice between RAM drive B: and R:

Edited by psc, 06 June 2007 - 08:56 AM.
New Upload

I just used the Control Panels ImDisk gui interface to increase the size of the B Ramdrive without it having to format the drive of its contents. Very cool.

Another question that came to mind. If we use the default compression option of NTFS with the B drive, Will it save RAM space for its contents. Compared to the RAMdisk before.

A suggestion to add a shortcut Option to the Script to the Quicklaunchbar for ImDisk. Like the screenshot.
Makes it convenient to get to it. Now that it can officially be said that it can replace the RamDrive.

I just used the Control Panels ImDisk gui interface to increase the size of the B Ramdrive without it having to format the drive of its contents. Very cool.

Another question that came to mind. If we use the default compression option of NTFS with the B drive, Will it save RAM space for its contents. Compared to the RAMdisk before.

A suggestion to add a shortcut Option to the Script to the Quicklaunchbar for ImDisk. Like the screenshot.
Makes it convenient to get to it. Now that it can officially be said that it can replace the RamDrive.

There is a new version on the server, having the QL umbrella.

Peter

Thanks!

A new version is available on the nativeEx server.

Now it runs also in the minimum configuration.

Peter

A new version is available on the nativeEx server.

It contains Olof's latest version with the read-only ability.

Peter

A new version is available on the nativeEx server.

For W2003 format.com needs additionally VSSAPI.DLL

Peter

A new version is available on the nativeEx server.

For W2003 format.com needs additionally VSSAPI.DLL

Peter

I have try with W2003 source and have error ATL.DLL not find
With RamDisk no error
So I have add this line in ImDisk.script

CopyOrExpand,"%SourceDir%\I386\Atl.dll","%TargetDir%\i386\system32"

and it work

I have try with W2003 source and have error ATL.DLL not find
With RamDisk no error
So I have add this line in ImDisk.script

CopyOrExpand,"%SourceDir%\I386\Atl.dll","%TargetDir%\i386\system32"

and it work

Thanks, pedrole15

Fixed and new version sent to server.

Peter

Hi Peter!

Please add:

%scriptdir%\ramdisk.script

On the disable list of this script to disable the ramdisk.script when the user selects all scripts from the treeview (otherwise both ramdisk and imdisk are added).

Or isn't Imdisk meant to replace ramdisk.script?

Hi Peter!

Please add:

%scriptdir%\ramdisk.script

On the disable list of this script to disable the ramdisk.script when the user selects all scripts from the treeview (otherwise both ramdisk and imdisk are added).

Or isn't Imdisk meant to replace ramdisk.script?

Peter

EDIT:

In the first read of your post I did not remember: In Verify there is already:

If {%RAMDisk:Main.Selected%} Then

"$$$ and RAMDisk exclude each other!";

Edited by psc, 17 June 2007 - 02:54 PM.
Additional Info

Peter

EDIT:

In the first read of your post I did not remember: In Verify there is already:

If {%RAMDisk:Main.Selected%} Then

"$$$ and RAMDisk exclude each other!";

Yes, but this is meant for the user when he is selecting imdisk from the main window before running the project.

This would avoid unneeded clicks and warning messages..

Yes, but this is meant for the user when he is selecting imdisk from the main window before running the project.
This would avoid unneeded clicks and warning messages..

Before I add your suggestion, please some more discussion:

I hate if my PC decides (sometimes wrong!) what I really want to do.
Look at WinWord when (German rule) you go into the next field of a table. When you write (intentionally) the first word starting with a lowercase letter, Bill G. decides that he knows it better and changes to uppercase.

Now the same with WinBuilder

I remember the troubles I have had with Explorer script.
The project contained BootSDI, and whenever I selected Explorer, WinBuilder told me by message box that RAMdisk also has been selected.
I had to

• Confirm the message
• Deselect RAMDisk

Big help? No unneeded clicks? Not an unnecessary warning message?

Ok, the actual 'exclude' is a little bit different. But it does not change my 'general meaning':

Automatic changes by the app are only allowed, if the user explicitely agrees to 'auto'

Peter

Ok - I agree with you about the point that you mention, I also don't like one bit of Word 2007 because they've "hidden" most of the tools I was so used to work with on Word 2003 and now it's really hard to be productive as before (although people say that's it's needed some time to get used but I don't have this sort of complaint regarding powerpoint and excel for example)...

I'll trust your word on the automatic selection of choices since too much automatic thinking also softens the intelect sometimes..

But this case happened because I downloaded the minimum version - which by default comes without wbverify, but still downloads both ramdisk and imdisk scripts.

I clicked to select all scripts from the root of the project and both ramdisks were added - shouldn't just one script be selected or available to download from the minimum profile for most cases and avoid confusions with double ramdisks?