[Wraith]

Good to hear!

*contemplates giving longhorn a go...*

[killerbee]

hi wraith,

i stumbled across a problem while installing as i have slept. i tried to use XPInstall via RunOnceEx to install sth. after first reboot. But the "|" won't be recognized to set another .xml-file.

It is possible to use a normal switch for another .xml-file, like a "-c filename.xml"?
This would be great, as i don't know if a \| will do the trick in RunOneEx for me

Cya

Killer Bee

[Wraith]

To be honest, I'd rather not, my argument parsing routines have never really been bulletproof when not given argc/argv[]

I'd rather keep it as filename after a certain character...

here's the ones I'd contemplate using, as they CAN'T be used by the file system:

\ / : * ? " < > |

(You can get this list by typing one of them in when renaming a file)

So... which one would people prefer? Which is least destructive when dealing with INF's and command lines and registry?

I'm going to add %XPINSTALL% so it'll allow files in the XPinstall dir. This SHOULD function in the program arguments, in the XML, as well as the command line.

Will just make it easier if you put XPinstall in a certain directory with all the others inside it.

I guess that'll be ready for v1.3

I'm going to bed... might dream up some inspiration

[killerbee]

have some nice dreams wraith,

i hope u can extract %1% from XPInstall %1% then we don't need a command line switch. Should run with "XPInstall test.xml" so i can use it from RunOnceEx. ATM i call it from a second directory with the original filename so it is usable from RunOneEx.

Cya

Killer Bee

[big_gie]

Is it me or the link is v1.1 and not v1.2?

Can't wait for the alternate xml file! Well, can't wait for v1.3...

[killerbee]

hi,

yeah, the link here must be V1.1 as there is no information about colors in the actual xpinstall.zip from voidfx.com

Cya

Killer Bee

[shawn26]

Hello All,

have i to create a $OEM$ and $1 Folder?

Like this: C:\XPCD\$OEM$\$1

or is this not possible for xpinstall?

Many ThX!

Shawn26

[EskimoPie]

The readme says its v1.1.

[killerbee]

@shawn,

u can use the $OEM$-Folder structure if u like. XPInstall will work with it. XPInstall is just a very cool way to Install Hotfixes and Applications.
It can be used to replace .cmd-files and RunOnceEx after first reboot. Also u can use it along with .cmd or RunOnceEx.

This is much better than slipstreaming all Hotfixes into svcpack.inf as u will get a progress baar instead of a taking a long time T-13min Stage.

Cya

KillerBee

[prathapml]

Hey, the bugtracker page itself has a bug - "You must select the category of the bug" before reporting the bug. So couldn't post it there.

A feature request:
I'd like to use the %CD% variable in XPinstall. Should be simple enough, query the location from where the XPinstall executable is run.
There's many other system variables added newly, but I see that this variable (which I'd previously requested) wasn't there. It's very crucial because then you can get folders/files under the location where XPinstall.exe is resident.

For example, program='%CD%\apps\814995 /S.EXE'

[Trip-]

as was said previously in this post,
%SourcePath% works just fine instead of %cd%

[Wraith]

Sorry ppl, mustn't have uploaded properly.

I'm moving them onto a subdomain for my website, I'll put the versions in the filenames. Don't suppose anyone still has v1.0 lying around? I'd like to keep them all there.

For the moment, http://xpinstall.voidfx.com/downloads/
I'll have a proper site up soon. After v1.3.

[killerbee]

hi wraith,

i have v1.0 lying around on my machine at home. I can upload it later when i'm at home again.


cya

Killer Bee

[mendipjohn]

I downloaded an early version - v0.9.9. Is that what you need?

[prathapml]

YAY, I too can get coloured XPinstalls done now. I'll see what new I can do with it.


Linux/FreeBSD based server ?
(refer to wraith's post below)

||
||
||
V

This post has been edited by prathapml: 26 January 2004 - 03:09 PM

[Wraith]

I don't recall making a 0.9.9... would be interesting to see

The download link in the first post points to 1.2 now.
I figured out the problem... I had 1.2 as XPinstall.zip, and 1.1 as xpinstall.zip. The wonders of case-sensitive filenames

EDIT: The easiest way to tell what version it is is by doing a file properties on it, and selecting the version tab.

[mendipjohn]

Oops... wrong prog!

[Sunil]

gotta say, THIS IS NICE, improves over the old install routine of just waiting and watching the progress bar move.

[Wraith]

@prathapml
Remove the attachment. Got it on the server.

[Wraith]

XPinstall 1.3 has been added, check the website for changes since 1.2.