Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!cs.utexas.edu!sun-barr!newstop!sun!stpeter.Eng.Sun.COM!cmcmanis From: cmcmanis@stpeter.Eng.Sun.COM (Chuck McManis) Newsgroups: comp.sys.amiga.tech Subject: Re: Unit names -> : Message-ID: <136985@sun.Eng.Sun.COM> Date: 10 Jun 90 07:51:02 GMT References: <03378.AA03378@ufweed.UUCP> <9006082114.AA03862@human-torch.lockheed.com> Sender: news@sun.Eng.Sun.COM Organization: Sun Microsystems, Mt. View, Ca. Lines: 18 If you are interested in tracking down the culprit to this problem I have a couple of suggestions. What is probably happening is that the DeviceNode for the disk is getting munged (or the Volume node) and the string which makes up the device name (a bstr) is getting set to either \0 or \01\0 which is the same in bstr terms. This is most likely caused by a bug in either a file requestor routine, a directory utility, or another program that is getting cute by scanning the device list. The problem may be that the pointer to a device name is being used without being cleared and that could stomp on the device name. You might consider exchanging notes about what sort of directory like utilities y'all have in common. That would be my first guess anyway. -- --Chuck McManis Sun Microsystems uucp: {anywhere}!sun!cmcmanis BIX: Internet: cmcmanis@Eng.Sun.COM These opinions are my own and no one elses, but you knew that didn't you. "I tell you this parrot is bleeding deceased!"