Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Microcap & Penny Stocks : FRANKLIN TELECOM (FTEL) -- Ignore unavailable to you. Want to Upgrade?

To: Mr. Cellophane Man who wrote (22105)	11/25/1997 6:54:00 AM
From: SoliRA	Read Replies (2) \| Respond to of 41046

Dan, You said "Even though I'm usually connected at 28 or 33Kbps, from the time I hit "NEXT" until the time the next screen come up can take anywhere from 10-30 seconds." I'm connected at 21.6kbs, but can zip through messages an average of one every 2.7 seconds ( I just timed myself through a series). Of course, if I want to stop and READ them, it takes longer... If it's taking you 10 or 30 seconds to download a message your computer configuration needs tweaking. A faster system may work better. If my guess is right, you're using a 60MHz pentium or 100MHz 486 currently.

To: Mr. Cellophane Man who wrote (22105)	11/25/1997 8:55:00 AM
From: (Bob) Zumbrunnen	Read Replies (2) \| Respond to of 41046

off-topic: off-topics and slow SI The same discussion about off-topics is happening in the SYCR thread right now, too. Mention was made there of something like another thread for stuff not directly related to the company. As for slow response to the Next button, whenever I have this problem, clearing both my disk cache and memory cache in my browser seem to cure them, especially the disk cache. Everytime you load a new page, the cache must be searched to see if the page contains any previously-saved elements. If you've got a large cache (8 meg or so) and it's full, it can take a LONG time. 8 meg of hard drive must be read, and if it's found that you're loading a page that's not cached (which will always be the case when reading new messages), the browser has to determine which cached page is the oldest, delete it, and save the new one. I used to run an 8-meg cache, but now only use 4-meg, and clear it frequently. Anytime I see really crappy browser performance, it's always a full cache. You can check the fullness of your cache by typing "About: Cache" in your browser's location box.