Opened 8 years ago

Closed 8 years ago

#561 closed defect (wontfix)

Annoying defaults installing WPI archive

Reported by: yoda Owned by: David Azarewicz
Priority: minor Milestone: Release 4.00
Component: Installer Version: 3.21.02
Keywords: Cc:


Installer now seems to override any users changed options. That is a very bad idea, as this can cause problems.


ACPI.CFG is overwritten Default is "LID=suspend" On my laptop this means, that that the system is dead, as suspend/resume doesn't work (and never will). At least "LID=none would be fail-safe for all systems; but again, it is a bad idea to override users choice.

Config.sys is overwritten. Found 1 system now, where suspend/resume actually works; but only when /VBE is used. If I install a new version, that will get removed, and the system will be useless after resume. Bad idea again to override users defaults.

I can foresee same issue on my servers, that require /VW due to SCSI drivers. If that /VW gets removed, the server can't boot - an unacceptable thing to happen for a remote update.

We really need to get the installer to be more fail-safe and or intelligent, than it currently is.

Change History (3)

comment:1 Changed 8 years ago by diver

config.sys is no problem, as you just have to tell wpi not to adjust config.sys. but the acpi.cfg override is really annoying.

comment:2 Changed 8 years ago by yoda

I agree, that this is possible, but I still believe, that you can not expect all users to remember such a thing; and if they forget it, it will make their system end in a deadlock.

That is IMHO not a very good way to do it.

I am aware, that this is done to get rid of obsolete historical parameters; but we need a better solution.

For ACPI.CFG an idea could be, to create it with another filename, and maybe in another dir. Instead of distributing the file in WPI archive, make acpidaemon create it, if it is missing. That way it will never be overwritten.

comment:3 Changed 8 years ago by David Azarewicz

Resolution: wontfix
Status: newclosed

Improvements have already been made to the installer in recent releases, some of which may or may not address your concerns. Sorry, but the way the installer works now is the way it has to be. It may change in the future only if installation requirement change.

Note: See TracTickets for help on using tickets.