Workbench issue

[rkauer]

list all > contents.txt

The space between all & > is necessary.

 

[nineoc]

Well now, ain't this interesting:

Typed the following:

list (space) all (space) all (space) > (space) contents.txt

System request window opens with the same initial error message that prompted all this: Volume Workbench is full Retry Cancel

Hitting cancel produces the following shell line:

list: unable to open redirection file
8.Workbench:>


?????????

 

[desiv]

You need the RAM:contents.txt in there.
Otherwise it will try to write contents.txt to your FULL drive..

desiv

 

[nineoc]

I'm beginning to think that this :banghead: is an initiation ritual that you guys have dreamed up for Nepophytes.

Following your latest instructions, I type:

list all > Ram:contents.txt

The hard drive on the machine gronks a bit, then I get the following line in the Shell:

8.workbench:>

Glad you don't charge by the hour.



---------- Post added at 18:43 ---------- Previous post was at 18:35 ----------

Okay, got the book out to review Using The Shell.

Watch for smoke.

 

[ajk]

Following your latest instructions, I type:

list all > Ram:contents.txt

The hard drive on the machine gronks a bit, then I get the following line in the Shell:

8.workbench:>

Yes, this is what is supposed to happen. "list all" generates a list of everything in the location you run the command (which should be the system drive, if you gave the "cd sys:" command earlier). "> ram:contents.txt" relays the listing to a file on the Ram Disk called contents.txt.

Once it's done, you can browse that file with any text reader/editor, I suggested Multiview earlier because it should always be installed with Workbench. Therefore, "multiview ram:contents.txt" will display the file.

You can't leave out spaces, and you can't put "all" in the command twice, as the computer does not know a typo from a genuine command

 

[nineoc]

Thanks. My apologies. The second all is a typo in the post. It was not in the shell prompt.

Typing list all > Ram:contents.txt properly still does not bring up the required information.

Cannot find the contents.txt anywhere.

See below:

Did the following:

Typed cd Ram:

Shell line reads 8.Ram Disk:>

Typed multiview ram:contents.txt

Shell line reads Couldn't open contents.txt

Typed "list"

Shell line reads

disk.info 1137
ENV Dir
Clipboards Dir
T Dir
1 file - 3 directories - 9 blocks used

Can open ENV and T only. Says Clipboards is not mounted. Same with disk.info file.

:shrug:

 

[ajk]

That does not seem possible. Either there is still a typo somewhere or something is really screwed up in your system. In any case ENV and T etc. are not of any interest here.

How about if you just do "cd sys:" and "list all", this should print the list directly in the shell as it scans the drive.

 

[nineoc]

I agree, but have done it several times, and as you say, I may have done it incorrectly, but ----

Have just followed your recent instructions and the list is spooling.

I suppose at this point the only thing to do is to stop it once in a while to read it?

Yes, no, or?

---------- Post added at 23:50 ---------- Previous post was at 23:49 ----------

Just to make sure, would you care to type the exact path, and I will follow it to the letter?

---------- Post added at 23:52 ---------- Previous post was at 23:50 ----------

BTW: Opened ENV and T just as an exercise in accessing a DIR.

 

[ajk]

Yeah, you can stop it and check it bit by bit. The whole idea of re-routing it to a file was exactly to make it easier to examine. Still don't quite understand why that would not work, but perhaps you can find something out even like this.

The syntax is just "> volume:filename", so "list all > ram:contents.txt" should produce the listing on the Ram Disk, in a file called contents.txt. I did test it and it worked fine on my basic 3.1 install in WinUAE, but I am now at work, and can't make further tests until the evening unfortunately.

 

[nineoc]

OK. It just stopped, so will go through it again.

---------- Post added at 23:57 ---------- Previous post was at 23:54 ----------

Am I still looking for the contents.txt file?

---------- Post added at 23:58 ---------- Previous post was at 23:57 ----------

OK, thanks.

Just about my bedtime anyways.

Thanks again for your help, and enjoy your day.



---------- Post added 12th July 2012 at 00:26 ---------- Previous post was 11th July 2012 at 23:58 ----------

Just went through it again, and no sign of contents.txt.

Am off for a cup of tea, and then to bed.

:tired:

 

[rkauer]

Forget about redirection, just type:

dir ALL | more (the "|" is the one over the \ signal in the upper part of the keyboard, left of the backspace key)

And check the directories and files.

List is bit more comprehensive, but LS replaced it in some workbench versions.

 

[nineoc]

Okay, will try this later this eve when I get back to the Amiga.

 

[nineoc]

Hello:

Typed the following after the default line that says workbench:>

dir space ALL space | space more

Reply is Wrong number of arguments

Am going out shortly for the afternoon.

:huh:

 

[cosmicfrog]

not sure why your redirection is`t working but what I want know is

T, which contains a directory called samba-locks, and another book icon called turboprint.log

If these are in Ram:T
how did they get there

now as the dir T is just a tempory store you can safely delete these files
so everything in "sys:t" or as I think you have got it "Workbench:t" both should go to same place, this should make a little bit of space to start with.
easy way do this in workbench is show all files open up T show all files again, select all and delete.

but if files are not in "sys:t" but are there every time thats 2 apps to explore straight away

wondering if you are running out of mem for the contents file you trying create with the list cmd, so how much memory you got and what ver of Workbech are you using

If worst comes to worst you can always plug drive into a pc and use WinUAE to copy its contents but we not near that stage yet

EDIT just reread post #5
and you seem to have created contents.txt fine there

EDit2:
rereading post #7
RAM 578K 578 0 100% Ram disk

thats a lot of stuff in ya ram disk

humm on ya desktop the icon Workbench is probably the drive it boots from DH0:
it might be worth holding both buttons down after a reset/power on for the early boot memu and see if you can boot off QDH0 which if you friend did a good job it be Workbench.old, I would`t be happy modifying anything unless I knew I could boot the machine into a reasonable state, might be worth noting if any other hard drive partitions are bootable but I getting ahead here, best stick to one problem at a time

one the bright side you got plenty of free space its just spread over QDH1-Programs.old, DH2-Programs, WDH3-Four and WDH4-Five

 

[nineoc]

Hi CF:

Just passing by the Forum, and saw your post. Will review again when I have a mo, and comment.

Thanx for the input.