From: manaster@yu1.yu.edu (Chaim Manaster)
Newsgroups: comp.os.os2.misc,comp.periphs.scsi,comp.sys.ibm.pc.misc,comp.sys.ibm.pc.hardware
Subject: Can not delete files or partition volume name.
Date: 24 Jan 93 03:04:24 GMT
Followup-To: comp.os.os2.misc
Organization: Yeshiva University

I have a strange problem relating to DOS, OS/2 and scsi.
I have just added a scsi adapter (Bualogic 747s) to my EISA
computer (AMI enterprise II, 486/33) motherboard). Previously I
only had a WEstern Digital ESDI controller and one harddrive on it.
So I now have two controllers with one hard drive each.

I have several partitions on the original hard drive and one small
OS/2 (FAT) partition that I am using to get used to OS/2. I also
use stacker V. 2.0. Thus, on the ESDI drive I have the following:
	c:		Primary dos partition.
	d:, e:, f: 	Logiacl drives on the extended DOS partit.
	g:		Ramdrive
	h:-k:		Stacker uncompressed partit. for c:-f:

When I added the scsi drive I partitioned it so as to only create
an extended partition. Thus this created g: and bumped all the
other letters up by one. I then formatted the partition in DOS.
It seemed like all was OK.

THen I accessed the scsi drive from OS/2. The drive g: appeared as
an Icon so I thought all was OK. Then I tried to double click on it
and it replied with a sys00045 error. It gave the option to RETRY
which I did, and it worked OK and accessed the tree for that scsi
drive. However, when I tried again, it did the same thing, exactly,
same error message and then worked on retry. 

I called IBM tech support and the entry level support told me to
reformat using the IBM OS/2 format program which would also work
for the DOS side of the computer. I tried that.

In fact, I tried to repartition, using OS/2 fdisk (for the scsi
drive only), and reformatting. WHen I got back to the DOS side of
hte computer, the g: partition now had a VOLUME name: with 3
characters that I can't reproduce. The first (and third) character
is a degree symbol (a small circle) which I can reproduce by
holding down alt and pressing 248 on the keypad. The middle
character is an uparrow (which I can not reproduce at all! Some
tables show this as 024 on the ascii table, but the alt 024 entry,
just beeps at me, but does not produce a character.)

In order to delete this partition in DOS, fdisk requires the name
of the VOLUME, and I have no way of entering it!!
I have tried to delete the partition in OS/2, but when Irecreate
the partition (in OS/2 or DOS) that same 3 character VOLUME name is
still there!
The system (Idon't know wheter it is OS/2 or DOS) has also given me
(at first one file, now up to three files) three files with wierd
filenames (example: female symbol, up arrow, 0, and the like), with
either zero length, short length, or 4,246,357,685 bytes being
reported when you dor a DIR under DOS (this is near the addressing
capability of the CPU)! 
I CAN NOT DELETE these files no matter how I tried both under DOS,
and under OS/2.
I tried using 	DOS delete
		Lotus Magellan - by highlighting the filenames, F3
		OS/2 dragging to shredder (got a sys00002 error
			that the files do not exist!)
		OS/2 delete object

None of the above worked! The files still persist.

I Then ran chkdsk g: /f on both the DOS and OS/2 sides of the
system. There were some crosslinked files which the system took
care of, but these file still persisted and were not eliminated,
although the reported file sizes became 0, 0, 1,435,237 (THis was
the file that perviously was 4 gig+).

What is going on? How do I get rid of these bothersome files.
How do I enter the wierd characters in the filenames and the VOLUME
name of the partition?
Is there something basic that is wrong.?
I am using the btdosm.sys and btmdisk.sys supplied by Buslogic for
the scsi driver, and using the generic OS/2 int 13 driver.

Perhaps related to this is the fact that although the btmdisk.sys
is loaded in the config.sys by a device= line, when I actually boot
up, it reports that it was not loaded, without giving a reason as
to why not. However, but for the above wierd problems, everything
seems to work OK so far, (I just got it up, have not really worked
it out to see if any other bugs.).

Thank you very much for the help.

Henry Manaster
manaster@yu1.yu.edu

-- 
***************************************************************************
	Henry Manaster          *     EMail: manaster@yu1.yu.edu
	Brooklyn, NY            *
                                *
	Disclaimer: The above is not necessarily MY opinion nor that 
				of anyone else :-)  ????!
****************************************************************************
 
Newsgroups: comp.os.os2.misc