-- update all and .bat scripts in NSIS install

[Kulyok]

So far I've been happily using .bat file suggested by the_bigg. (And soon enough I wasn't alone in it. It's good, hence it's pretty popular). Just to remind you:

@echo off
echo "The setup program is updating itself, please be patient..."
"Setup-Xan.exe" --update-all > nul
cls
echo "Version 4" | pause > nul
"Setup-Xan.exe"

It seems to work perfectly on my XP machine. However, recently, Accolon, who did some testing for Xan's friendship, said that this .bat didn't work on Accolon's machine, and I wonder if it's a serious issue. I'll try to translate:

"Setup-XanBG1Friend.exe" --update-all 1>nul  line doesn't work. (Copying in nul).
Kulyok: it's update-all > nul, as I posted before. But anyway.

I recommend changing "Setup-XanBG1Friend.exe" --update-all 1>nul
to "Setup-XanBG1Friend.exe" --update-all 1>MyModTempFile.txt
and then deleting MyModTempFile.txt

... because the way it is, installation stops, and bat exits on my machine.

Would you(a general you, if you understand what it all means) please explain to me if there is a real problem, and if I indeed should change anything?

[the bigg]

If there's a problem, then it's a M$ problem for not maintaining stuff across versions of Windows. Which one does he use? 32 or 64 bit? Runs as Guest, as User or as Admin?

[Kulyok]

Okay, I've directed him to this topic at aerie.ru.

[Accolon]

May be M$, may be not.

Admin: dir > nul
XP: The system cannot find the file specified.
Admin: nul
XP: ' ' is not recognized as an internal or external command, operable program or batch file.
Admin: dir > NULL or dir > null
System reply with empty string (I'm happy  )


AMD Athlon (tm) 64 Processor
3200+ 
2.01 GHz, 1,00 Gb of RAM

Started & work as Admin.

Microsoft Windows XP [Version 5.1.2600] SP 2.
Log files of fixes:
10 383 KB873339.log
 6 023 KB885250.log
 7 009 KB885523.log
 5 072 KB885626.log
 5 749 KB885835.log
 5 615 KB885836.log
 4 319 KB885884.log
 5 543 KB886185.log
 5 521 KB887472.log
 6 240 KB887742.log
 5 470 KB888113.log
 5 471 KB888302.log
 7 796 KB890046.log
10 655 KB890859.log
 7 949 KB891781.log
 9 411 KB893066.log
10 193 KB893756.log
10 158 KB893803v2.log
12 103 KB894391.log
22 842 KB896358.log
11 881 KB896422.log
11 623 KB896423.log
12 717 KB896424.log
11 866 KB896428.log
17 502 KB896688.log
13 723 KB898458.log
16 011 KB898461.log
16 153 KB899587.log
16 648 KB899588.log
16 737 KB899591.log
 6 132 KB900485.log
18 613 KB900725.log
33 336 KB901017.log
 5 217 KB901190.log
17 573 KB901214.log
25 377 KB902400.log
21 827 KB904706.log
22 719 KB905414.log
46 072 KB905749.log
27 691 KB905915.log
 5 282 KB908519.log
 5 238 KB908531.log
23 058 KB910437.log
 6 036 KB911280.log
 6 725 KB911562.log
25 647 KB911564.log
28 026 KB911565.log
 6 987 KB911567.log
 7 407 KB911927.log
12 809 KB912812.log
11 426 KB912919.log
11 387 KB913446.log
12 644 KB913580.log
13 139 KB914388.log
13 456 KB914389.log
20 257 KB916281.log
 5 462 KB916595.log
 5 749 KB917159.log
 6 248 KB917344.log
 5 268 KB917422.log
27 242 KB917734.log
 6 072 KB917953.log
 6 795 KB918118.log
 6 615 KB918439.log
13 565 KB918899.log
10 468 KB919007.log
11 760 KB920213.log
10 447 KB920214.log
 9 831 KB920670.log
10 015 KB920683.log
10 650 KB920685.log
11 968 KB920872.log
 9 869 KB921398.log
 9 973 KB921883.log
12 162 KB922582.log
10 833 KB922616.log
18 687 KB922760.log
12 704 KB922819.log
10 632 KB923191.log
12 797 KB923414.log
19 119 KB923689.log
 6 274 KB923694.log
 3 943 KB923723.log
 6 461 KB923980.log
 6 008 KB924191.log
 7 695 KB924270.log
 7 048 KB924496.log
 5 517 KB924667.log
11 623 KB925398.log
14 142 KB925454.log
11 017 KB925486.log
11 506 KB925720.log
12 945 KB925902.log
 1 223 KB926247.log
 6 390 KB926255.log
 6 647 KB926436.log
 9 520 KB927779.log
 9 801 KB927802.log
10 781 KB927891.log
17 163 KB928090.log
 7 158 KB928255.log
 7 127 KB928843.log
 8 207 KB929338.log
 7 053 KB929969.log
 7 613 KB930178.log
 7 691 KB930916.log
 8 255 KB931261.log
15 138 KB931768.log
13 058 KB931784.log
19 605 KB931836.log
13 423 KB932168.log
20 248 KB933566.log
13 573 KB935448.log

[the bigg]

my Windows XP uses `nul'. If other versions of Windows use `null', then who is to take the blame? 

[Accolon]

the bigg: If other versions of Windows use `null', then who is to take the blame?

Well, it is not matter in any case. How about use "> MyModTempFile.txt" and erase "MyModTempFile.txt" after processing, instead using "> null" in bat-file? BGT v1.04 installation, for example, will crash, until bat file will not to be fixed.