14 replies to this topic

[Max_Real Qnx]

Hi my friends

http://technet.micro...y/cc753194.aspx

Syntax and Options of MKLINKMKLINK [[/D] | [/H] | [/J]] Link Target/D - Creates a directory symbolic link. Default to file symbolic link./H - Creates a hard link instead of a symbolic link./J - Creates a Directory Junction.Link - Specifies the new symbolic link name.

Example: (cmd.exe)This command is working.mklink /d /j C:\Link X:\Windows


Why this command isn't working ?

mklink /d /j X:\Link X:\Windows

I thanks right now for answers

[was_jaclaz]

Is X: NTFS formatted?

If NO, it's normal that it won't work.

If YES:

Try junction:
http://technet.micro...s/bb896768.aspx

Or this:
http://www.codeproje...tionpoints.aspx

Or this:
http://www.rekenwond...m/linkmagic.htm

Or this:
http://schinagl.priv...nkshellext.html

Even if they don't work, they may give you a hint about what the problem might be.



jaclaz

[Lancelot]

Or junc from Olof Lagerkvist
(I love to use it )
http://www.ltr-data.se/files/junc.zip
web page: http://www.ltr-data.se/opencode.html

[joakim]

I would be interested to see your bcd store if you make this.

Btw, it's a wim format limitation that is preventing you from making hardlinks/junctions on X:\ in vistape;

http://www.boot-land...?...ost&p=66385

Joakim

[joakim]

Mklink.exe works if vista is run from HD without wim.

Win7pe also works with mklink if native-booted from vhd.

Joakim

[paraglider]

I just create a small ram disk using imdisk. Then I junction from b:\programs to sources\programs.wim. Would be nice however to have a writable wim on a read only media. It appears that the write filter only works on the boot.wim

[joakim]

I just create a small ram disk using imdisk. Then I junction from b:\programs to sources\programs.wim. Would be nice however to have a writable wim on a read only media. It appears that the write filter only works on the boot.wim

Wims can be mounted read-only on many different file systems, however mounting read-write is only supported on NTFS destinations.

The reason why it works on boot.wim is because it´s mounted on a tiny 3Mb ntfs partition located inside boot.sdi.

What may be possible, is to add a second partition to boot.sdi and possibly also choose to map a custom wim to it, or map some other precreated ntfs disk/partition image to it and thereby be allowed to make junction points on it.

Joakim

[paraglider]

My ram disk is NTFS formatted. Both boot.wim and programs.wim are directly on the CD. Yet the mounted boot.wim is writable. Any attempt to mount the programs.wim in the ram disk with the read / write option results in an error being returned. I could of course copy the programs.wim to the ram disk and mount it from there. However I then would not gain the ram savings gained by splitting the programs from boot.wim.

[sanbarrow]

just a thought .... paraglider - if you wrap the wim in a vmdk and mount that with /undo: <path> first
you may be able to mount the wim read / write even if its on CD ... never mind - just thinking loud

[joakim]

My ram disk is NTFS formatted. Both boot.wim and programs.wim are directly on the CD. Yet the mounted boot.wim is writable. Any attempt to mount the programs.wim in the ram disk with the read / write option results in an error being returned. I could of course copy the programs.wim to the ram disk and mount it from there. However I then would not gain the ram savings gained by splitting the programs from boot.wim.

Sounds strange that you can´t mount rw on a ntfs ramdisk. When you say mounted boot.wim, do you mean X: as a whole?

[Galapo]

just a thought .... paraglider - if you wrap the wim in a vmdk and mount that with /undo: <path> first
you may be able to mount the wim read / write even if its on CD ... never mind - just thinking loud

Yes, that's what may work. This is exactly what the WimPack script for LiveXP does so that the mounted WIM can be writable (just that changes can't be committed).

Regards,
Galapo.

[paraglider]

I think the reason that boot.wim x: drive is writable is because the boot load process copies the wim file into ram and mounts it from there.

[paraglider]

How do you create a vmdk file? And how is it mounted at boot time?

[Galapo]

Created with fsutil.exe and mounted at boot with ImDisk.

Regards,
Galapo.

[paraglider]

I used the following:

fsutil file createnew programs.vmdk 73400320
vdk open 0 programs.vmdk /rw /L:z /p:0
format z: /fs:NTFS /X
vdk ulink z:
vdk close 0

However when I then try to load the image with:

vdk open 0 programs.vmdk /L:z /p:0 /UNDO:d:\vdk

I get an error reported:

Failed to decide type of 'programs.vmdk'.
Open as a simple sector image file.
Failed to create a REDO log.
The parameter is incorrect.