Re: Installed VA C++ 3 in eComstation 1.2, hangs on startup

Brent White wrote:

> I have a problem.  I installed Visual Age C++/2 v3.0 on my eComstation
> box, then changed the resolution to 1024x768 32-bit and rebooted.
> Ctrl-Alt-Delete only reboots (so that nice CAD commander has not loaded
> yet)
> 
> Now it just sits there with a blank desktop.  Subsequent reboots won't fix
> the problem.
> 
> Is there a way I can diagnose this or just get back to what it was on the
> last good boot?

This has been biting everyone since, what, 98?  Boot to a command line and
edit comfig.sys to point the som*** files in your \os2 directory.  Somir=
has to point to the DSOM subdirectory - find the directories pointed to in
config.sys refering to SOM and then find the corresponding subdirectories
in \os2.  After the first few times, I learned to not let the installer
modify config.sys to get past that PITA - it wants to point to what were
updated SOM files when it was released but which are now badly outdated.

You have the updates for VAC++?  If not contact me, but I think they are
still out on one of the IBM servers somewhere.  They will make life a lot
nicer for you, in case you haven't found out yet.

-- 

I have a problem.  I installed Visual Age C++/2 v3.0 on my eComstation 
box, then changed the resolution to 1024x768 32-bit and rebooted.  
Ctrl-Alt-Delete only reboots (so that nice CAD commander has not loaded 
yet)

Now it just sits there with a blank desktop.  Subsequent reboots won't fix 
the problem.

Is there a way I can diagnose this or just get back to what it was on the 
last good boot?

On Sun, 27 Jan 2008 05:30:14 UTC, Will Honea <whonea@yahoo.com> wrote:

> > I have a problem.  I installed Visual Age C++/2 v3.0 on my
eComstation
> > box, then changed the resolution to 1024x768 32-bit and rebooted.
> > Ctrl-Alt-Delete only reboots (so that nice CAD commander has not
loaded
> > yet)
> > 
> > Now it just sits there with a blank desktop.  Subsequent reboots won't

> > fix the problem.
> 
> This has been biting everyone since, what, 98?  Boot to a command line and
> edit comfig.sys to point the som*** files in your \os2 directory.  Somir=
> has to point to the DSOM subdirectory - find the directories pointed to in
> config.sys refering to SOM and then find the corresponding subdirectories
> in \os2.  

While he's at it, he should make sure the IBMCPP directories are at the END
of the LIBPATH statement instead of the beginning.  

-- 
Alex Taylor
Fukushima, Japan
http://www.cs-club.org/~alex

Alex Taylor wrote:

> On Sun, 27 Jan 2008 05:30:14 UTC, Will Honea <whonea@yahoo.com>
wrote:
> 
>> > I have a problem.  I installed Visual Age C++/2 v3.0 on my
eComstation
>> > box, then changed the resolution to 1024x768 32-bit and rebooted.
>> > Ctrl-Alt-Delete only reboots (so that nice CAD commander has not
loaded
>> > yet)
>> > 
>> > Now it just sits there with a blank desktop.  Subsequent reboots
won't
>> > fix the problem.
>> 
>> This has been biting everyone since, what, 98?  Boot to a command line
>> and
>> edit comfig.sys to point the som*** files in your \os2 directory. 
Somir=
>> has to point to the DSOM subdirectory - find the directories pointed
to
>> in config.sys refering to SOM and then find the corresponding
>> subdirectories in \os2.
> 
> While he's at it, he should make sure the IBMCPP directories are at the
> END of the LIBPATH statement instead of the beginning.

That's a good idea as well.  You can also get into some real cock-ups with
the toolkit positions in those paths - getting VACPP 3 to co-exist with
version 4 was a challenge because of paths.  I finally wound up using batch
files to reset the environment and launch whichever version I wanted to use
via the beginlibpath and session level set= lines with no mention of the
compiler specific paths in config.sys.  In the long run, that was the
simplest way all around.  For the linker, be sure to set the DPATH or it
will barf on message lines.

-- 

Will Honea wrote:

> Brent White wrote:

>> I have a problem.  I installed Visual Age C++/2 v3.0 on my eComstation
>> box, then changed the resolution to 1024x768 32-bit and rebooted.
>> Ctrl-Alt-Delete only reboots (so that nice CAD commander has not
loaded
>> yet)
>> 
>> Now it just sits there with a blank desktop.  Subsequent reboots won't
fix
>> the problem.
>> 
>> Is there a way I can diagnose this or just get back to what it was on
the
>> last good boot?

> This has been biting everyone since, what, 98?  Boot to a command line and
> edit comfig.sys to point the som*** files in your os2 directory.  Somir=
> has to point to the DSOM subdirectory - find the directories pointed to in
> config.sys refering to SOM and then find the corresponding subdirectories
> in os2.  After the first few times, I learned to not let the installer
> modify config.sys to get past that PITA - it wants to point to what were
> updated SOM files when it was released but which are now badly outdated.

> You have the updates for VAC++?  If not contact me, but I think they are
> still out on one of the IBM servers somewhere.  They will make life a lot
> nicer for you, in case you haven't found out yet.

How do I boot to a command prompt?