Jump to content

[SOLVED] RunOnce stage - NLITE.CMD wont run .exe


Recommended Posts

No.

This has seemingly not passed through.

If you want to mount a .iso (or any other kind of similar image) you need a driver.

The driver needs to be installed. (this is not up to debate).

So what is needed is at the very least BOTH the driver file (.sys) and the .exe (command line tool) at the very minimum, then there is generally[1] the need of either a .inf or of a .reg file to actually install the driver.

Honestly I cannot remember if a reboot is really-really needed for filedisk (I tend to believe it is not really required for the basic functionality needed but it needs to be checked by experiment), you might need a "helper" to install without rebooting, see the (already given link, where a few examples are posted):

https://msfn.org/board/topic/38118-filedisk-virtual-disk-driver-for-windows-nt2kx/

BUT this is still available via Wayback Machine:

https://web.archive.org/web/20061026071810/http://www.benlaufer.com/2006/04/24/filedisk-ua/

and it seems to me like it doesn't do anything particular about the install.

As well the "complete" package is still available here:

http://www.jeffothy.com/weblog/filedisk-iso-mounter/

(of course you will need to strip out the extension .dll)

About the 7zip SFX there is no particular issue with setting a path in a SFX, it is a bit of time I don't fiddle with 7zip SFX, but you can use the excellent:

https://sourceforge.net/projects/s-zipsfxbuilder/

to easily build a SFX with the modified module by Oleg Shcherbakov (which has a number of handy additions to the "normal" SFX module).

In it the same path where the SFX is is simply (no use of "temp" directory):

InstallPath="%%S"

(of course this needs to be on a read/write location)

jaclaz

 

[1] Some drivers need not this as they are (smartly) coded to have these internally to the.exe and also sport "telescopic" commands, a good example is Ken Kato's VDK (which is not suitable for your use as it mounts .img (or .img+.pln) and not .iso 

 

Link to comment
Share on other sites


Another possibiliy (this can surely be installed/uninstalled) on the fly is to use good ol' MS VSS SDK driver.

http://reboot.pro/topic/6492-virtual-storage-driver/

The download is a mass of bloat (around 23 MB) but what you really-really need is just three files:

virtualstorage.sys (58 KB, the driver)

virtualstorage.inf (2 KB, the install info)

vstorcontrol.exe (42 KB the command line tool)

In a nutshell (example):

C:\VSS\VSS2>vstorcontrol install
Removing all virtual drives
Installing Virtual Bus Driver... Succeeded

C:\VSS\VSS2>vstorcontrol create cd-rom -image C:\downloaded\Ylmf_OS_3.0.iso
Virtual Storage v5.2 Build 3790.1208

Creating drive backed by C:\downloaded\Ylmf_OS_3.0.iso ...
Waiting for drive initialization...............
Drive     : \\.\Cdrom4
Drive ID  : {5E3FEF3D-3910-11E9-B0E3-001FC6BB76CE}
Type      : CD-ROM
Size      : 676MB
1 volume(s) on this drive:
    \\?\Volume{5e3fef3e-3910-11e9-b0e3-001fc6bb76ce}\
        F:\

C:\VSS\VSS2>dir F:
 Il volume nell'unità F è Ylmf_OS_3.0
 Numero di serie del volume: 4095-D7B3

 Directory di F:\

20/04/2010  10.28    <DIR>          .disk
31/05/2010  12.05               211 README.diskdefines
31/05/2010  03.48             4.055 Readme_en-US.txt
31/05/2010  03.48             7.558 Readme_zh-CN.txt
31/05/2010  03.46             7.558 Readme_zh-TW.txt
18/05/2010  08.37               144 autorun.inf
31/05/2010  11.54    <DIR>          casper
06/04/2010  21.23    <DIR>          install
31/05/2010  08.52    <DIR>          isolinux
31/05/2010  12.05             4.204 md5sum.txt
06/04/2010  21.23    <DIR>          pics
27/05/2010  01.06    <DIR>          preseed
22/05/2010  10.23         1.473.629 wubi-hd.exe
17/05/2010  09.50         1.473.237 wubi.exe
               8 File      2.970.596 byte
               6 Directory               0 byte disponibili

C:\VSS\VSS2>vstorcontrol remove F:
Virtual Storage v5.2 Build 3790.1208

Removing...
Drive     : \\.\Cdrom4
Drive ID  : {5E3FEF3D-3910-11E9-B0E3-001FC6BB76CE}
Type      : CD-ROM
Size      : 676MB

C:\VSS\VSS2>vstorcontrol uninstall
Removing all virtual drives
Uninstalling Virtual Bus Driver... Succeeded

but also:

C:\VSS\VSS2>vstorcontrol install
Installing Virtual Bus Driver... Succeeded

C:\VSS\VSS2>vstorcontrol create cd-rom -image C:\downloaded\Ylmf_OS_3.0.iso
Virtual Storage v5.2 Build 3790.1208

Creating drive backed by C:\downloaded\Ylmf_OS_3.0.iso ...
Waiting for drive initialization...............
Drive     : \\.\Cdrom7
Drive ID  : {5E3FEF3F-3910-11E9-B0E3-001FC6BB76CE}
Type      : CD-ROM
Size      : 676MB
1 volume(s) on this drive:
    \\?\Volume{5e3fef40-3910-11e9-b0e3-001fc6bb76ce}\
        F:\

C:\VSS\VSS2>vstorcontrol uninstall
Removing all virtual drives
Uninstalling Virtual Bus Driver... Succeeded

BTW a good thing is that this driver does provide (while mounting the cd-rom) a tooltip on the application bar, like "Found new hardware looking for driver", "Found new hardware CD-ROM", "The new hardware installed correctly and is ready for use"

Though when you uninstall/remove the device you have a message "You can now remove the CD-ROM" that may confuse the final user.

jaclaz

Link to comment
Share on other sites

  • 2 months later...

APologies for my absence

FilediskA is exactly what I need. i.e.The ability to load / autorun any .iso in one double-click proceduce (for machines without iso tools previously installed).

The relevant iso is the only way to install the software (its distributed this way). Those who download the iso may not know how to mount it and so would apprecite the simplicity of a single exe next to the iso itself, which can be distributed alongside the iso.

Upon trying FilediskUA, the issue arises that upon clicking the iso to mount it (after FilediskUA has been installed) the iso doesn't autoplay / autorun the installer splash screen. I seek a way to run autorun automatically and this likely would require a separate vbs/cmd script, in turn necessitating a self extracting archive. However as I have already expressed in previous post, SFX can either unload files into current dir. or into a temp dir. More ideal is by way of latter, where files [filediskUa installer, script] are unloaded to temp directory, where the script of which not only installs filediskUA and subsequently mounts the relevant iso (thats beside the SFX) but also runs the autoplay of that iso - and that all of these steps occur upon clicking the SFX.exe.

The quesiton is, how may a script in the now temp folder 'retrieve' the directory [nominally a string] from which the SFX that spit it out ab inito, is located?

 

What i've done so far:

In a folder theres a custom installer, itself a SFX, which installs IMDISK without reboot.
Separately theres a cmd script, which when clicked mounts the iso + launches the autorun - this script resides adjacent to the iso. In this state, there are 3 files, 2 if not counting the iso. To merge those 2 would be ideal.

 

Open to all suggestions. I should mention this should work on all windows XP to present.

 

 

Edit: filediskuA does not appear to work and is temperamental when mounting.

Edited by shorterxp
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...