Rubyinstaller users - May 2005 - Windows 2000 Server install trouble

When I try to install 1.8.2-14 or 15 on my Windows 2000 Server box, I
get bizarre results: the install proceeds about 15-20 percent, then I
start getting write errors!  I retry and each one succeeds up to about
20-25% done, then I get a fatal write error and have to cancel out.
Once I''ve done this, the Windows 2000 OS is done for the session; I
have
to reboot to do anything more of any kind, such at look at a file shared
from another system; the OS tells me there are insufficient resources.

I''m not expert with W2000 or Windows in general, so I don''t
know where
to look for causes.  Any clues?

--
Isn''t sanity just a one-trick pony anyway? I mean, all you get is that
one trick, rational thinking, but when you''re good and crazy, well, the
sky''s the limit! The Tick

Bradford Hull wrote:
> When I try to install 1.8.2-14 or 15 on my Windows 2000 Server box, I
> get bizarre results: the install proceeds about 15-20 percent, then I
> start getting write errors!  I retry and each one succeeds up to about
> 20-25% done, then I get a fatal write error and have to cancel out.
> Once I''ve done this, the Windows 2000 OS is done for the session;
I have
> to reboot to do anything more of any kind, such at look at a file shared
> from another system; the OS tells me there are insufficient resources.
> 
> I''m not expert with W2000 or Windows in general, so I
don''t know where
> to look for causes.  Any clues?
I would check your hard disk for errors, particularly your system drive 
(usually he C drive) and whatever disk you are trying to install Ruby on 
(by default that would also be the C drive):

- Open Window Explorer
- Right-click on the drive you want to check
- Click on the "Tools" tab
- In the "Error checking" box, click on "Check Now..."
- Check both options and press "Start"

Scanning for bad sectors can take a long time, so do this when you
don''t
need your system for a while (like over night).

You should also make sure your paging file is big enough (it should be 
at least two times the amount of RAM in your machine):

- On the desktop, right-click on My Computer and select Properties
- Click on the Advanced tab
- Click on the Performance Options button
- Click on the Change" button
- Make sure the initial size is at least two times your RAM size
- The Maximum size can be three or four times your RAM size.

Curt

Done; this seemed like a good idea.  No errors were found, and when I
tried again afterwards I got the same thing, plus on reboot the system
decided the D drive needed a chkdsk again.  It''s a pretty clear
pattern;
when I try to install, the system acts like the registry is overfull
afterwards until I reboot (for example, when I try to look at a shared
disk, it says there are insufficient system resources to attach to it).
After a reboot, it goes back to normal.  However, it is notable that the
system did have a vastly bloated registry, due to repeated registry of
new stuff without removing the old outmoded files'' registries first;
that''s what I was installing Ruby for, was to run registry cleaner I
had
written to remove the rubbish.


--
On Wed, 2005-05-25 at 13:57 -0500, Curt Hibbs wrote:
> Bradford Hull wrote:
> > When I try to install 1.8.2-14 or 15 on my Windows 2000 Server box, I
> > get bizarre results: the install proceeds about 15-20 percent, then I
> > start getting write errors!  I retry and each one succeeds up to about
> > 20-25% done, then I get a fatal write error and have to cancel out.
> > Once I''ve done this, the Windows 2000 OS is done for the
session; I have
> > to reboot to do anything more of any kind, such at look at a file
shared
> > from another system; the OS tells me there are insufficient resources.
> > 
> > I''m not expert with W2000 or Windows in general, so I
don''t know where
> > to look for causes.  Any clues?
> 
> I would check your hard disk for errors, particularly your system drive 
> (usually he C drive) and whatever disk you are trying to install Ruby on 
> (by default that would also be the C drive):
> 
> - Open Window Explorer
> - Right-click on the drive you want to check
> - Click on the "Tools" tab
> - In the "Error checking" box, click on "Check Now..."
> - Check both options and press "Start"
> 
> Scanning for bad sectors can take a long time, so do this when you
don''t
> need your system for a while (like over night).
> 
> You should also make sure your paging file is big enough (it should be 
> at least two times the amount of RAM in your machine):
> 
> - On the desktop, right-click on My Computer and select Properties
> - Click on the Advanced tab
> - Click on the Performance Options button
> - Click on the Change" button
> - Make sure the initial size is at least two times your RAM size
> - The Maximum size can be three or four times your RAM size.
> 
> Curt
**> Never let a computer see you hurry. <** Bradford K. Hull

In the same dialog where you set the size of the paging file, you can 
also set the maximum size of your registry... you might want to try that.

Curt

Bradford Hull wrote:
> Done; this seemed like a good idea.  No errors were found, and when I
> tried again afterwards I got the same thing, plus on reboot the system
> decided the D drive needed a chkdsk again.  It''s a pretty clear
pattern;
> when I try to install, the system acts like the registry is overfull
> afterwards until I reboot (for example, when I try to look at a shared
> disk, it says there are insufficient system resources to attach to it).
> After a reboot, it goes back to normal.  However, it is notable that the
> system did have a vastly bloated registry, due to repeated registry of
> new stuff without removing the old outmoded files'' registries
first;
> that''s what I was installing Ruby for, was to run registry cleaner
I had
> written to remove the rubbish.
> 
> 
> --
> On Wed, 2005-05-25 at 13:57 -0500, Curt Hibbs wrote:
> 
>>Bradford Hull wrote:
>>
>>>When I try to install 1.8.2-14 or 15 on my Windows 2000 Server box,
I
>>>get bizarre results: the install proceeds about 15-20 percent, then
I
>>>start getting write errors!  I retry and each one succeeds up to
about
>>>20-25% done, then I get a fatal write error and have to cancel out.
>>>Once I''ve done this, the Windows 2000 OS is done for the
session; I have
>>>to reboot to do anything more of any kind, such at look at a file
shared
>>>from another system; the OS tells me there are insufficient
resources.
>>>
>>>I''m not expert with W2000 or Windows in general, so I
don''t know where
>>>to look for causes.  Any clues?
>>
>>I would check your hard disk for errors, particularly your system drive 
>>(usually he C drive) and whatever disk you are trying to install Ruby on
>>(by default that would also be the C drive):
>>
>>- Open Window Explorer
>>- Right-click on the drive you want to check
>>- Click on the "Tools" tab
>>- In the "Error checking" box, click on "Check
Now..."
>>- Check both options and press "Start"
>>
>>Scanning for bad sectors can take a long time, so do this when you
don''t
>>need your system for a while (like over night).
>>
>>You should also make sure your paging file is big enough (it should be 
>>at least two times the amount of RAM in your machine):
>>
>>- On the desktop, right-click on My Computer and select Properties
>>- Click on the Advanced tab
>>- Click on the Performance Options button
>>- Click on the Change" button
>>- Make sure the initial size is at least two times your RAM size
>>- The Maximum size can be three or four times your RAM size.
>>
>>Curt
> 
> **> Never let a computer see you hurry. <** Bradford K. Hull
>

Please disregard this whole thread: the system''s registry had over a
million bogus entries!?!  Once I got it cleaned up (no small feat) there
were no further problems.  Thanks for the advice, Curt;  it helped what
I ended up doing, even if it didn''t let the Ruby installer work
immediately.

--
On Thu, 2005-05-26 at 13:35 -0500, Curt Hibbs wrote:
> In the same dialog where you set the size of the paging file, you can 
> also set the maximum size of your registry... you might want to try that.
> 
> Curt
> 
> Bradford Hull wrote:
> > Done; this seemed like a good idea.  No errors were found, and when I
> > tried again afterwards I got the same thing, plus on reboot the system
> > decided the D drive needed a chkdsk again.  It''s a pretty
clear pattern;
> > when I try to install, the system acts like the registry is overfull
> > afterwards until I reboot (for example, when I try to look at a shared
> > disk, it says there are insufficient system resources to attach to
it).
> > After a reboot, it goes back to normal.  However, it is notable that
the
> > system did have a vastly bloated registry, due to repeated registry of
> > new stuff without removing the old outmoded files'' registries
first;
> > that''s what I was installing Ruby for, was to run registry
cleaner I had
> > written to remove the rubbish.
> > 
> > 
> > --
> > On Wed, 2005-05-25 at 13:57 -0500, Curt Hibbs wrote:
> > 
> >>Bradford Hull wrote:
> >>
> >>>When I try to install 1.8.2-14 or 15 on my Windows 2000 Server
box, I
> >>>get bizarre results: the install proceeds about 15-20 percent,
then I
> >>>start getting write errors!  I retry and each one succeeds up
to about
> >>>20-25% done, then I get a fatal write error and have to cancel
out.
> >>>Once I''ve done this, the Windows 2000 OS is done for
the session; I have
> >>>to reboot to do anything more of any kind, such at look at a
file shared
> >>>from another system; the OS tells me there are insufficient
resources.
> >>>
> >>>I''m not expert with W2000 or Windows in general, so I
don''t know where
> >>>to look for causes.  Any clues?
> >>
> >>I would check your hard disk for errors, particularly your system
drive
> >>(usually he C drive) and whatever disk you are trying to install
Ruby on
> >>(by default that would also be the C drive):
> >>
> >>- Open Window Explorer
> >>- Right-click on the drive you want to check
> >>- Click on the "Tools" tab
> >>- In the "Error checking" box, click on "Check
Now..."
> >>- Check both options and press "Start"
> >>
> >>Scanning for bad sectors can take a long time, so do this when you
don''t
> >>need your system for a while (like over night).
> >>
> >>You should also make sure your paging file is big enough (it should
be
> >>at least two times the amount of RAM in your machine):
> >>
> >>- On the desktop, right-click on My Computer and select Properties
> >>- Click on the Advanced tab
> >>- Click on the Performance Options button
> >>- Click on the Change" button
> >>- Make sure the initial size is at least two times your RAM size
> >>- The Maximum size can be three or four times your RAM size.
> >>
> >>Curt
> > 
> > **> Never let a computer see you hurry. <** Bradford K. Hull
> > 
> 
Reports of my death have been greatly exaggerated. Mark Twain