[Alpheratz13]

Evening,

What are the swiches for install VIA Hyperion 4in1 4.53v?
Or how i do that?
Someone knows?

Thank you

Irving

[Rodent]

from my runonceex.cmd:

Quote

REG ADD %KEY%\167 /VE /D "VIA Hyperion 4in1 4.53" /f
REG ADD %KEY%\167 /V 1 /D "%CDROM%\Install\Applications\via4in1_4.53\Setup.exe -s" /f

-s means you first got to extract the single .exe to get all neccessary install files,
then use setup.exe -R command to create a setup.iss file in C:\Windows\

drag this setup.iss in the same folder of extracted via setupfiles,
then run setup.exe -s

rgds
alex

[Alpheratz13]

Thanks alots for your help

[prathapml]

Well, it gets to be a stumbling block to use the installer.
What if you use this CD on a PC that is not based on the VIA chipset? Either the install fails, or it will show a dialog-box and stall the install - which makes it not unattended anymore. And what happens if the VIA drivers actually get installed on an intel-chipset based system? jeez.... frightening.

Of course, its no worry if you're only doing this for one PC - this post is just to caution you about the possible problem that could happen. And people lend out their uA CDs to their friends too (for a minute, don't consider its legality) - so if you give your CD to your friend, he'll end up facing instability, because of VIA drivers on non-VIA hardware.

You need to rather extract the 4-in-1 driver file, and use it through the OEMpnpDriversPath method - from winnt.sif.

[Rodent]

hi there,

i am sorry,
i only will use the uA cd on my own pc, so i did not thought about muliti-chipset-compatibility.

thanks for that idea prathapml

rgds
alex

[Alpheratz13]

Ok, if i understood what you said, is better i install VIA after install unattend windows, right?
Thanks

Irving

[CoffeeFiend]

It is during the install. You have to setup the path in your winnt.sif. (just like you'd do for all your other drivers) It's definately the better way to do it. Otherwise, you'd have to have a way to detect what chipset is in the PC. It's not really a hard thing to do, but there's lots of work involved to do it and to maintain it with every new chipset (and find the information every time).