Dave, Im using ZM/hT and specifying the path where it should find the z80 snapshots, hence the reference to 48k_ and 128K_ . sadly, when I specify pth1_ it would appear that ZM/hT only looks at the first directory of pth1_ and not the others.
Not a problem, just a bit of a shame. Neil >>> [EMAIL PROTECTED] 22 February 2007 15:26 >>> Neil, I think you will find it can! As I understand it the PTH device intercepts OPEN calls for files so finds them in all the given locations. In the case of the DIR command it successfully opens the first item in the path, so does not look any further. As mentioned you need to be careful when using it with files you intend to write. This will always succeed in the first element of the path, so if you delete a file on the path, and then try and create a new instance, the new instance will not necessarily appear in the same folder as the one you just deleted. Note that Phil's documentation should be on one of the documentation disks as the file PATH.TXT. In terms of using quotes around the filename, I get into the habit of doing this as it allows for characters that would not be valid if used without quotes. Dave -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Riley Sent: 22 February 2007 14:34 To: [EMAIL PROTECTED] Subject: Re: [ql-users] c68 guide for one who wants to know. I see, so even though pth1_ seems to be a list of separate directories, it doesn't fully work like that, therefore if an application asks for where to look for it's data, you can't just use pth1_ expecting the application to see all the data even if you've setup pth1_ to point to all the places where that data should exist. Shame that ! Neil >>> [EMAIL PROTECTED] 22 February 2007 13:37 >>> Neil Riley scripsit:: > Dave > > in your example.... > > LRESPR win1_PTH_rext > PTH_ADD "win1_C68BIN_" > PTH_ADD "win1_QJUMP_" > PTH_ADD "win1_SYS_" > PROG_USE "PTH1_" > > Id expect DIR PTH1_ to show all objects in C68BIN , QJUMP & SYS. > > In my example i have two directories 48k and 128k ( and they are > directories off win1_) > > so ( and it seems the "" aren't really necessary ) > > 10 LRESPR rom1_pth_rext > 20 PTH_ADD "win1_48k_" > 30 PTH_ADD "win1_128k_" > 40 PROG_USE "PTH1_" > > Id expect dir pth1_ to show all objects in 48K and 128K but it only > shows > objects in 48K !?! swapping lines 20 and 30 shows only the objects in > directory > 128k ! > > Argh ! > > Neil > > PTH is not used like that. PTH is good for your binaries' location. When it failed to find the binary in the first directory, it looks on the next, and so on. PROG_USE "PTH1_" is fine. DATA_USE "PTH1_" is dangerous: opening existing document is fine, but creating new file is a bad idea! Saving is also bad. PTH*_ devices are chained, so dir pth1_ show first directory, dir pth2_ the next... and so on. pth_list might be your friend too. *********************************************************************************** The contents of this email are confidential to the intended recipient. It may not be disclosed to or used by anyone other than the addressee, nor may it be copied in any way. If received in error, please contact the company on 01793-715380, then delete it from your system. Please note neither the company nor the sender accepts any responsibility for viruses and it is your responsibility to scan attachments (if any) for viruses. No contract may be concluded on behalf of the company by means of email communications. BC Services (UK) Limited (trading as Boxclever), Technology House, Ampthill Road, Bedford, MK42 9QQ. Registered No. 5290544 England www.boxclever.co.uk *********************************************************************************** _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
