MUI_PAGE_DIRECTORY on Windows 2003 File-Cluster

saschagottfried · 27th October 2008, 08:21

Hi everybody,

I stumbled over an uncommon situation where the MUI-builtin MUI_PAGE_DIRECTORY (I am still using MUI.nsh Version 1) did not choose the proper disk for space calculation in target directory.

There is the following directory structure on his Windows 2003 File-Cluster. I do not know how to setup such things, but it seems to be some kind of mounting several disks to create such a directory structure. But this is not the subject of this thread. Obviously this seems to be possible with this OS.

W: <first disk - old harddisk with capacity of 13MB>
W:\GSI$GSIRoot <second disk - lots of GB space>
W:\GSI$GSIRoot\Application\Setups <third disk - lots of GB space>

The target directory is:
W:\GSI$GSIRoot\Application\Setups\Programs\Other\VDE-Normen\VDE 8.0

That means it is addresses a folder on the third hdd with lots of space. The MUI_PAGE_DIRECTORY however DOES NOT ENABLE the 'NEXT' button and shows a free space of 13MB. Apparently the calculation of space is always using the root of the path - what is working in 99.9 % of all use cases. But here it maps to the 13 MB disk, instead of detecting this uncommon directory mapping to the big harddisk.

I used MUI_DIRECTORYPAGE_VERIFYONLEAVE to ship around that and offered an IGNORE button to continue. But until today I thought the builtin MUI page could handle it all.

Is it possible for NSIS to detect such situations? What about other installers - are those aware of such things? Is anyone familiar with this situation? It would appreciate when the answer to this question will be merged into the NSIS MUI code, thus everybody can create installers that pass such situations as well.

saschagottfried · 29th October 2008, 08:45

Until now I had no reply. I want to emphasize that this reported behaviour of NSIS could be a next item on the bug tracker. I would like some of the forum senior members to comment this.

kichik · 7th November 2008, 21:28

Which version of NSIS are you using? This should already be working fine on the latest versions.

saschagottfried · 8th November 2008, 19:43

Thanks kichik for taking care of my concerns...

The NSIS version that compiled this setup was either 2.36 or 2.37

I my previous posts I did not highlighted that much that a major customer of my company has reported this behaviour and sent me screenshots showing the behaviour I reported in detail. That's why I was not able to test or reproduce it in the meantime and decided to ask the community first of all.

What can I do next to help?

kichik · 8th November 2008, 21:05

It was fixed in 2.38, so try building a new installer with the latest version and have them test it.

saschagottfried · 25th November 2008, 11:48

Thanks kichik!

It was definitely the bug you mentioned. Thanks for being a reliable part of this community.

27th October 2008, 08:21	#1
saschagottfried Member Join Date: Aug 2006 Location: Germany Posts: 54	MUI_PAGE_DIRECTORY on Windows 2003 File-Cluster Hi everybody, I stumbled over an uncommon situation where the MUI-builtin MUI_PAGE_DIRECTORY (I am still using MUI.nsh Version 1) did not choose the proper disk for space calculation in target directory. There is the following directory structure on his Windows 2003 File-Cluster. I do not know how to setup such things, but it seems to be some kind of mounting several disks to create such a directory structure. But this is not the subject of this thread. Obviously this seems to be possible with this OS. W: <first disk - old harddisk with capacity of 13MB> W:\GSI$GSIRoot <second disk - lots of GB space> W:\GSI$GSIRoot\Application\Setups <third disk - lots of GB space> The target directory is: W:\GSI$GSIRoot\Application\Setups\Programs\Other\VDE-Normen\VDE 8.0 That means it is addresses a folder on the third hdd with lots of space. The MUI_PAGE_DIRECTORY however DOES NOT ENABLE the 'NEXT' button and shows a free space of 13MB. Apparently the calculation of space is always using the root of the path - what is working in 99.9 % of all use cases. But here it maps to the 13 MB disk, instead of detecting this uncommon directory mapping to the big harddisk. I used MUI_DIRECTORYPAGE_VERIFYONLEAVE to ship around that and offered an IGNORE button to continue. But until today I thought the builtin MUI page could handle it all. Is it possible for NSIS to detect such situations? What about other installers - are those aware of such things? Is anyone familiar with this situation? It would appreciate when the answer to this question will be merged into the NSIS MUI code, thus everybody can create installers that pass such situations as well.

7th November 2008, 21:28	#3
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,336	Which version of NSIS are you using? This should already be working fine on the latest versions. NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

8th November 2008, 21:05	#5
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,336	It was fixed in 2.38, so try building a new installer with the latest version and have them test it. NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

29th October 2008, 08:45	#2
saschagottfried Member Join Date: Aug 2006 Location: Germany Posts: 54	Until now I had no reply. I want to emphasize that this reported behaviour of NSIS could be a next item on the bug tracker. I would like some of the forum senior members to comment this.

8th November 2008, 19:43	#4
saschagottfried Member Join Date: Aug 2006 Location: Germany Posts: 54	Thanks kichik for taking care of my concerns... The NSIS version that compiled this setup was either 2.36 or 2.37 I my previous posts I did not highlighted that much that a major customer of my company has reported this behaviour and sent me screenshots showing the behaviour I reported in detail. That's why I was not able to test or reproduce it in the meantime and decided to ask the community first of all. What can I do next to help?

25th November 2008, 11:48	#6
saschagottfried Member Join Date: Aug 2006 Location: Germany Posts: 54	Thanks kichik! It was definitely the bug you mentioned. Thanks for being a reliable part of this community.