Mail Archives: opendos/2000/10/30/23:54:26
Hi Chad,
----- Original Message -----
From: <fernande AT internet1 DOT net>
To: <opendos AT delorie DOT com>
Sent: Sunday, October 29, 2000 8:27 PM
Subject: Re:
> That was me, Chad, not Mark :-)
Sorry about that I probably skimmed down too far and got the wrong name. It
will take me a while to get used to this format. I am used to writing
messages on FIDOnet and my reader/editor combe would take out all of those:
>>
>>>
>>>>
>>>>>
etc. and reduce them to just one >. So trying to figure out who is saying
what to whom sometimes gets a little bewidering. I used to gripe about those
on FIDO and tewll them to get a decent reader. I use Spped Read and Seedit
in DOS for reding FIDO mail. Some of those quotes would go past 70
characters per line and you had a real mess. This stupid OE doesn't even
have a wrap setting on it so I can set it to 72 characters and automatically
the reset the quotes. Stupid peice of MS crap. Gates Strikes Agian!!!!
> The two problem areas that come to mind were SciTech Display Doctor, and
> the Wipe function of Norton Utilities. Both would cause EMM386 to halt
> the system, or crash, no matter what I tried. I can't remember what
> exactly I tired, However, it has been too long :-)
Oooops, I just wrote a message about WIPEDISK. I don't use it very much, I
use Central Point BULKERAS that came with COPYIIPC. WIPEDISK only wipes the
data in the sectors. BULKERAS erases everything including the sector
headers. But when I do run across those diskettes with a track zero error,
I'll use both WIPEDISK and BULKERAS. I have never had a problem with
WIPEDISK, but haven't used it in a while. So I'll give that one a shot on
both my computer and my brother's computer and see if either one gives me a
problem. I don't think I have ever use the Display Doctor you mentioned. Not
sure what it is. I do have some problems with programs not running with
EMM386 installed, but these are generally old programs or ones that cannot
have EMM386 of any kind installed. The DOCs will usually tell you to use
them with a clean boot.
> Recently, after switching the boot scsi adapter in another computer,
> Norton wipe crashes again. Let me explain further, both scsi adapter
> have been installed, I just switched the setup to boot from the
> Differential SCSI adapter, instead of the Single Ended one. This is
> under PCDOS 7, However. I am not worried about it, However. The setup
> is probably going to get changed again anyways :-)
I have a 3.1 Seagate Diff (HVD) drive here that I cannot use. I'll sell it
to you
for a good price. It is a full height drive. I even downloaded the manual
for it from Seagate. it is a used drive. It's boxed up and ready to go. My
stupid manual said that it had differential capability. I bought the drive
before I found out that this controller is really a single ended controller.
I paid nearly $200 for controller. Now I find out they sell the things for
around
$25. But I bought it a long time ago. It is a tyan NCR 53c825 controller.
BTW Symbios does not work worth a crap with this controller, takes a bunch
more memory and plain sucks. I went to the Tyan site after I found out from
NCR who made it and got their software, it is much better. Yet Symbios is
the
ones that produced the chipset! Go Figure. Actually, I think NCR made this
chipset before Symbios took it over. Anyway I won't buy another Symbios
piece of junk, my next one will use their chipset, but I'll get the Tekram
version. I am not certain what chipset Adaptec uses in their U2W. I am not
ready to go to 160mbs sysem, 80mbs seems good and is cheap now.
I also have my non-bootable controller installed but disabled the interrupt,
but WINDOZE crap still finds it, so I just disable it in the hardware. It is
on my Sound Blaster 16-SCSI-II card. It is a 6310/20 with no BIOS.
Just curious, how do you select which controller to boot from and which ID
to boot? I won't be able to do anything until I get a new MB, because this
one has the NCR 710/810 in BIOS and recognizes my card. Since I do not have
a FLASH BIOS I can't delete it, so I am stuck until I get another MB. I
could use other controllers, but not the Tekram. Tekram states that if I
have this in my BIOS I cannot use U2W controller until I delete that
portion of my BIOS. I just happen to have one version of that BIOS too early
and the stupid setup does not allow me to disable it. I swear that these
pinheads who write software don't have a clue about the real world.
I bought it because they claimed that the BIOS on the card is invisible to
the system and not up in the UBM area. But what the heck, I still have to
load the stinking drivers if I want to use the tape drive or CDROM or
Syquest. (well only if I want to loack and unloack the Syquest drive.) Six
of one, half a dozen of another. Can't win for losing.
Pat
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
- Raw text -