[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Before you purchase a Dell PC


  • To: Barry Robbins <brobbins@xxxxxxxxxxxx>
  • Subject: Re: Before you purchase a Dell PC
  • From: greene@xxxxxxxxxxxxxxx
  • Date: Wed, 28 Jan 1998 08:35:54 -0800 (PST)
  • In-reply-to: <3.0.3.32.19980126150915.00a24840@xxxxxxxxxxxxxxx>

PureBytes Links

Trading Reference Links

<x-html><HTML>

<PRE>Barry Robbins wrote:</PRE>

<BLOCKQUOTE TYPE=CITE>&lt;&lt;Just thought you might like to hear about
my experience with Dell...>></BLOCKQUOTE>
FWIW - I've spent the last 3 days buying and setting up a new computer
system for my husband (his 486 was ready for the trash can).&nbsp; On Monday
- I bought a Compaq 4540 (the new $999 model).&nbsp; The left speaker went
"snap, crackle and pop" all the time.&nbsp; I figured it was a bad unit
- so I took it back on Tuesday morning - and exchanged it for a new one.&nbsp;
The second unit had the same problem.&nbsp; So I called Compaq technical
support - which informed me that the problem was a defect in the soundcard
(in this model and many other Compaq models) - and it was "working on a
fix").&nbsp; I don't know about you - but when I buy a new computer - I
expect it to work ok when I take it out of the box.&nbsp; I don't feel
like waiting around for a "sound card fix".&nbsp; So I exchanged the Compaq
Tuesday afternoon for a HP (same kind of machine - about $100 more). So
far so good (except for the 2 days I wasted on the defective machines -
maybe I'll be back to normal in a day or two).&nbsp; So I guess the moral
of the story is that Dell isn't the only problem company around.

<P>BTW - the one company that I really liked in all of this was Office
Depot (where I bought the computers).&nbsp; It was absolutely terrific
in terms of handling the returns - no questions asked.&nbsp; Robyn</HTML>
</x-html>From ???@??? Wed Jan 28 20:50:54 1998
Received: from smtp1.nwnexus.com (smtp1.nwnexus.com [198.137.231.16])
	by mail1.halcyon.com (8.8.7/8.8.7) with ESMTP id UAA12888
	for <neal@xxxxxxxxxxxxxxxx>; Wed, 28 Jan 1998 20:49:22 -0800 (PST)
Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48])
	by smtp1.nwnexus.com (8.8.7/8.8.7) with ESMTP id UAA10833
	for <neal@xxxxxxxxxxx>; Wed, 28 Jan 1998 20:49:14 -0800
Received: (from smartlst@xxxxxxxxx)
	by mx1.eskimo.com (8.8.8/8.8.8) id UAA31275;
	Wed, 28 Jan 1998 20:48:10 -0800
Resent-Date: Wed, 28 Jan 1998 20:48:10 -0800
From: "Glenn Schultz" <glens@xxxxxxxxxxxxx>
To: "Omega List" <omega-list@xxxxxxxxxx>
Subject: Omega Post
Date: Wed, 28 Jan 1998 10:50:15 -0600
Message-ID: <01bd2c0c$ceb5e9e0$047a2399@xxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.71.1712.3
X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3
Resent-Message-ID: <"UCDka3.0.7e7.3e0qq"@mx1>
Resent-From: omega-list@xxxxxxxxxx
X-Mailing-List: <omega-list@xxxxxxxxxx> archive/latest/13661
X-Loop: omega-list@xxxxxxxxxx
Precedence: list
Resent-Sender: omega-list-request@xxxxxxxxxx
Status:  O

After all the Omega bashing a new concern is arising regarding new security
measures.  Since nobody knows what the security will be the idea that
passwords will expire or you will be charged is you need a new password when
you change machines or drives seems somewhat silly.

Following all the Omega bashing I became quite concerned and sent an e-mail
to the office of the president on Jan. 20.  Shortly thereafter I received an
e-mail which exactly matched the Omega Post.  My letter is copied below.  I
think that this incident disproves a great deal of the overall bashing and
shows responsiveness on the part of Omega.  As far as Y2k compliance is
concerned I am sure that a patch will be forth coming.  Overall, I will take
the 32 bit upgrade for $500 rather than work with the 16bit anyhow.

I am posting this message in an attempt to get more focus on system trading
and design.  Since I trade off a desk I forced in bid / offer trading
(basis) between sectors and structures.  As a result, I do not have the
system design skills that many of you have and would like to learn more.

Dear Sir,
I am a concerned TradeStation user and Omega stock holder.  I purchased
TradeStation as a step up from SuperCharts; primarily to get full access to
easy language.  My concerns are several:
First, I noticed on the Omega List many traders claiming that TS 4.0 was not
Y2K compliant.  I tested this for myself and verified that TS 4.0 is not Y2K
compliant.  Since I purchased TS 4.0 in July of 97 I assumed it would be
compliant.  Furthermore, I have not heard of a response on the part of Omega
regarding an effort to provide a fix for TS 4.0.  When will Omega produce a
Y2K compliant fix for TS 4.0 ?
Second, the bull market has produced a host of competitors offering similar
products.  Many of these products are  supposedly Y2K compliant -- However,
I cannot verify this for myself -- In addition, these products are also 32
bit.  I know that DJ telerate is 32 bit; I dont know if it is Y2K compliant.
Third, there has been a number of postings on the Omega list by both traders
and solution providers suggesting that users switch to other platforms such
as Windows on Wall Street etc.  They voice a number of concerns ranging from
the responsiveness of the organization in general to long wait times for
technical support.  I personally, have had positive experiences with both
the sales personnel (Mr.. Rodriguez and Mr. Riveria).  However, the voices
of discontent cannot be totally fabricated.
The above factors seem to suggest an organization that is violating some of
the cardinal rules of customer care.  I realize that announcing release
dates and time tables for fixes, patches, and upgrades places you between a
rock and a hard place if you miss the release date.  However, I would rather
see my stock price rise and have some information regarding the current
state of my TradeStation as opposed to nothing and reading posts that
suggest the Omega customer base is going to defect enmass to a competitor.
May I suggest the following a first and inexpensive step.  I know your
developers have a priority schedule of fixes, patches, and product upgrades.
You could e-mail or snail mail the priority schedule to your users without
mentioning time tables.  This would at least represent a positive step
regarding customer communication and mitigate speculation that Omega is out
of business in 2 years and their $2,000 software is useless at the same
time.
I am professional trader employed by a primary broker dealer.  You must
remember that when there are no facts to deal in most traders will deal in
rumor and speculation.  I assume it is the same for independent retail
traders as well.  Unfortunately, they will deal in runners that could well
cost Omega and its shareholders potential new sales and revenue expansion.
The bottom line is I like the product so I bought the stock.  Fortunately,
not at $11.00 -- but I never buy IPOs anyhow.  You stock is now selling at
10 times earnings when the SnP500 and Software stocks are selling at 20 and
36 times respectively.  I think your product and stock offer value but
recent posts (rumor, speculation, and to  large extent customer
dissatisfaction) have caused me some concern.
Sincerely,
Glenn M. Schultz