Sacramento Weekly Meet Discussion (dead meet, but how the SRIC started)
08-25-2004, 09:17 AM
#9886
Solberg regarding his crash in Germany.
wow, not one crack in the roll cage or the welding.
“I don’t want to make an excuse for what happened,” he said in his exclusive column for Motorsport News. “I lifted a bit for the crest, but we had new tyres and I didn’t warm them enough. They were still too cold, and we didn’t have enough grip. The car just slid sideways into the concrete.
“I’m very impressed with the standards at Subaru. Everything was well handled after the accident, with doctors and everything, but also the car itself is very good with the way it is welded and put together. We didn’t get one crack in the rollcage or in the welding. Somebody in Prodrive needs a big trophy. It was incredible after an accident like that.”
“I’m very impressed with the standards at Subaru. Everything was well handled after the accident, with doctors and everything, but also the car itself is very good with the way it is welded and put together. We didn’t get one crack in the rollcage or in the welding. Somebody in Prodrive needs a big trophy. It was incredible after an accident like that.”
08-25-2004, 09:21 AM
#9887
Warm Fuzzy Admin
iTrader: (45)
Join Date: Mar 2001
Location: Sacramento, CA
Posts: 13,799
Car Info: 97 LOB, 05 FXT, 03 Tundra
Holy crap. That's impressive.
And, once again, Petter impresses with his humility. He's got to be the nicest guy in WRC.
And, once again, Petter impresses with his humility. He's got to be the nicest guy in WRC.
Last edited by sybir; 08-25-2004 at 09:24 AM.
08-25-2004, 09:22 AM
#9888
VIP Member
iTrader: (2)
Join Date: Apr 2003
Location: pompous douchebag
Posts: 9,351
Car Info: $200,000 sports car
Originally Posted by sybir
I like having my stereo in the lower slot. Get a Legacy pocket with a door and it'll look clean when it's closed, too......
08-25-2004, 09:37 AM
#9889
Originally Posted by nKoan
Solberg regarding his crash in Germany.
wow, not one crack in the roll cage or the welding.
wow, not one crack in the roll cage or the welding.
08-25-2004, 09:39 AM
#9890
Warm Fuzzy Admin
iTrader: (45)
Join Date: Mar 2001
Location: Sacramento, CA
Posts: 13,799
Car Info: 97 LOB, 05 FXT, 03 Tundra
Luck and the fact that co-drivers sit on the floorboards for weight distribution, so he didn't have to duck down much, compared to someone in a road car in that situation.
08-25-2004, 09:41 AM
#9891
Originally Posted by sybir
Luck and the fact that co-drivers sit on the floorboards for weight distribution, so he didn't have to duck down much, compared to someone in a road car in that situation.
08-25-2004, 10:56 AM
#9894
Registered User
iTrader: (12)
Join Date: Nov 2002
Location: Reno, NV
Posts: 18,369
Car Info: 1993/2000/2001 GF4 mostly red
Originally Posted by sybir
Those things won't ever be removed, they're a part of the countryside. However, I'd guess we won't see any stages run on those roads anymore....
08-25-2004, 11:19 AM
#9895
VIP Member
iTrader: (2)
Join Date: Jun 2004
Location: ex-post whore
Posts: 5,152
Car Info: Aspin '02 WRX sedan
Ha Ha, my internet access is on the fritz again... so I have access to the Forums again here at work. I dunno how long it will take them to realize that I have full access again.
Hopefully they will over look me so that I can keep the access...
Hopefully they will over look me so that I can keep the access...
08-25-2004, 11:39 AM
#9897
BanHammer™
iTrader: (8)
Join Date: May 2000
Location: Wagonmafia Propaganda Lieutenant
Posts: 47,588
Car Info: 2001 Forester RS2 SPEC-F
Upgrading to Wife 1.0
Last a friend of mine upgraded from Girlfriend 4.0 to Wife 1.0 and found
that it's memory hog leaving few system resources for other applications.
He is now noticing the Wife 1.0 is also spawning Child-processes, which is
further consuming valuable resources. No mention of this particular
phenomenon was included in the product documentation, though other users
have informed me that this is to be expected due to the nature of the
application.
Not only that, Wife 1.0 installs itself so that it is always launched at
system initialization where it can monitor all other system activity. Some
applications such as PokerNight 10.3, BachelorParty 2.5 and PubNight 7.0
are no longer able to run on the system at all, causing the system to
lockup when launched (even though the apps worked fine before).
Wife 1.0 provides no installation options. Thus, the installation of
undesired plug-ins such as Mother-in-law 55.8 and the Brother-in-law Beta
is unavoidable. Also system performance seems to diminish each passing day.
Some features my friend would like to see in the upcoming Wife 2.0:
A "don't remind me again button"
A Minimize button
The ability to delete the "headache" file
An install feature that provides an option to uninstall 2.0 version
without loss of other system resources
An option to run the network driver in "promiscuous mode" allowing the
systems hardware probe to be much more useful/effective.
I myself wish I had decided to avoid all of the headaches associated with
Wife 1.0 by sticking with Girlfriend 3.0. Even here, however, I have found
many problems. Apparently you cannot install Girlfriend 4.0. You must
uninstall Girlfriend 3.0 first, otherwise the two versions of Girlfriend
will have conflicts over shared use of the I/O port.
Other users have told me that this is a long-standing problem that I
should have been aware of. Guess that explains what happened to versions 1
& 2.
To make matters worse, the uninstall program for Girlfriend 3.0 doesn't
work very well, leaving undesirable traces of the application in the
system. Another identified problem is that all versions of Girlfriend have
annoying little messages about the advantages of upgrading to Wife 1.0.
VIRUS ALERT
All users should be aware that Wife 1.0 has an undocumented bug. If you
try to install Mistress 1.1 before uninstalling Wife 1.0, Wife 1.0 will
delete MS Money files before doing the uninstall itself. Once that
happens, Mistress 1.1. won't install and you will get an "insufficient
resources" error message. To avoid the aforementioned bug, try installing
Mistress 1.1 on a different system and 'never'
run any file transfer applications (such as Laplink) between the two
systems.
Last a friend of mine upgraded from Girlfriend 4.0 to Wife 1.0 and found
that it's memory hog leaving few system resources for other applications.
He is now noticing the Wife 1.0 is also spawning Child-processes, which is
further consuming valuable resources. No mention of this particular
phenomenon was included in the product documentation, though other users
have informed me that this is to be expected due to the nature of the
application.
Not only that, Wife 1.0 installs itself so that it is always launched at
system initialization where it can monitor all other system activity. Some
applications such as PokerNight 10.3, BachelorParty 2.5 and PubNight 7.0
are no longer able to run on the system at all, causing the system to
lockup when launched (even though the apps worked fine before).
Wife 1.0 provides no installation options. Thus, the installation of
undesired plug-ins such as Mother-in-law 55.8 and the Brother-in-law Beta
is unavoidable. Also system performance seems to diminish each passing day.
Some features my friend would like to see in the upcoming Wife 2.0:
A "don't remind me again button"
A Minimize button
The ability to delete the "headache" file
An install feature that provides an option to uninstall 2.0 version
without loss of other system resources
An option to run the network driver in "promiscuous mode" allowing the
systems hardware probe to be much more useful/effective.
I myself wish I had decided to avoid all of the headaches associated with
Wife 1.0 by sticking with Girlfriend 3.0. Even here, however, I have found
many problems. Apparently you cannot install Girlfriend 4.0. You must
uninstall Girlfriend 3.0 first, otherwise the two versions of Girlfriend
will have conflicts over shared use of the I/O port.
Other users have told me that this is a long-standing problem that I
should have been aware of. Guess that explains what happened to versions 1
& 2.
To make matters worse, the uninstall program for Girlfriend 3.0 doesn't
work very well, leaving undesirable traces of the application in the
system. Another identified problem is that all versions of Girlfriend have
annoying little messages about the advantages of upgrading to Wife 1.0.
VIRUS ALERT
All users should be aware that Wife 1.0 has an undocumented bug. If you
try to install Mistress 1.1 before uninstalling Wife 1.0, Wife 1.0 will
delete MS Money files before doing the uninstall itself. Once that
happens, Mistress 1.1. won't install and you will get an "insufficient
resources" error message. To avoid the aforementioned bug, try installing
Mistress 1.1 on a different system and 'never'
run any file transfer applications (such as Laplink) between the two
systems.
08-25-2004, 11:53 AM
#9899
Registered User
iTrader: (12)
Join Date: Nov 2002
Location: Reno, NV
Posts: 18,369
Car Info: 1993/2000/2001 GF4 mostly red
Originally Posted by Egan
Dude that joke is older than you are.