home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.misc
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!spool.mu.edu!umn.edu!csus.edu!netcom.com!tnt
- From: tnt@netcom.com (Terry Turner)
- Subject: not startup.cmd (was: autostartup - it's gone on too long!)
- In-Reply-To: aaa@hpuerca.atl.hp.com's message of Wed, 16 Dec 1992 21:50:34 GMT
- Message-ID: <TNT.92Dec23145541@netcom.com>
- Sender: tnt@netcom.com (Terry Turner)
- Organization: Watch the Skies
- References: <TNT.92Dec16111557@netcom.com> <BzDGoB.CE3@hpuerca.atl.hp.com>
- Distribution: comp
- Date: Wed, 23 Dec 1992 22:55:41 GMT
- Lines: 28
-
- In article <BzDGoB.CE3@hpuerca.atl.hp.com> aaa@hpuerca.atl.hp.com (Simon Fowler) writes:
-
-
- In article <TNT.92Dec16111557@netcom.com>, tnt@netcom.com (Terry Turner) writes:
- > a friend _still_ has apps starting up that he setup to autostart under
- > os/2 1.3. he does not want them to startup and neither he nor i can get
- > them to stop coming up at startup. if anyone can help us stop them please
- > send me a note.
- >
- > background: he migrated his 1.3 desktop to 2.0 when he installed it (this
- > was last spring.summer) and these apps that he formerly wanted to have
- > start up were still coming up. there is no obvious way to stop them. he
- > has restartobjects set to startupfoldersonly and this does nothing to fix
- > this problem.
- >
- > my best guess is that the problem requires some work with an ini file
- > editor. has anyone tried this route?
-
- most respondents thought that it was due to an errant startup.cmd. this is
- not the case. thanks for the responses though. i failed to mention that
- these apps were formally (in 1.3) given the "startup on boot" property in
- the old program/properties dialog.
-
- this is a hole in the upgrade procedure between 1.3 and 2.0. the migration
- somehow preserves the behavior but does not allow the user to modify it.
- --
- terry
- tnt@netcom.com
-