T
Todd
Hi All,
I have an interesting design problem on a replacement computer
for a customer. I have her agreed to replace her current eight
year old computer with a new one, finally.
The current software she is running is a fancy POS (Point of
Sale, what did you thing I meant?) system that includes
billing, inventory, etc.. The software vendor requests
we stay with XP.
Now, here is the interesting part. Printing an invoice
drives them crazy as it can take up to five minute with
the customer tapping his foot in front of them. The
current system is two core. One of the cores is max'ed
out at 100% creating the print process. (The other core is
around 2 or 3 percent.) Soon as the core drops, the
printer starts. (I have asked the vendor when he will
multithread his stuff and he had no clue.)
So basically, I need to design a new computer that had
at least one core that is faster than h---. Probably
two core would be enough. (If the vendor ever multithreads,
I could always upgrade the processor.)
Anyone have any tips?
-T
I have an interesting design problem on a replacement computer
for a customer. I have her agreed to replace her current eight
year old computer with a new one, finally.
The current software she is running is a fancy POS (Point of
Sale, what did you thing I meant?) system that includes
billing, inventory, etc.. The software vendor requests
we stay with XP.
Now, here is the interesting part. Printing an invoice
drives them crazy as it can take up to five minute with
the customer tapping his foot in front of them. The
current system is two core. One of the cores is max'ed
out at 100% creating the print process. (The other core is
around 2 or 3 percent.) Soon as the core drops, the
printer starts. (I have asked the vendor when he will
multithread his stuff and he had no clue.)
So basically, I need to design a new computer that had
at least one core that is faster than h---. Probably
two core would be enough. (If the vendor ever multithreads,
I could always upgrade the processor.)
Anyone have any tips?
-T