maybe someone screwed with your filename and it is not an i but an L 😀
try this:
start Dosbox, got to that dir, type v and then hit TAB until the view.exe is shown and then press enter.

What's curious is that it's giving you a "File Not Found" error and not a "Bad Command or File Name" error - that tells me that, while DOSBox does acknowledge that the view.exe is there, view.exe is apparently looking for another file entirely before running, and failing to find said file, it quits with a File Not Found error.

That's just my speculation at this point, though - that may or may not be the case.

A totally different question: Why are you trying to use a screen capture program in DOSBox? Why not use the built-in screeshot function?

`Moe` wrote:

A totally different question: Why are you trying to use a screen capture program in DOSBox? Why not use the built-in screeshot function?

ha! I was unaware of this function. I was going with what worked for
me in the past capturing games and stuff.

thanks! =D

slow_poke wrote:

what would cause a "file not found" error message? I'm trying to get an old DOS screen capture going (The Grabber) and when I tr […]
Show full quote

what would cause a "file not found" error message?
I'm trying to get an old DOS screen capture going (The Grabber)
and when I try to run it (view.exe) it sez file not found..
hmmm 😕

slow_poke :

I'm afraid there's something wrong with your grabber installation anyway, judging by your test.tif

when I dir into my own grabber v3.98 directory, what I see is shown in
attached grabber.jpg

where's grpcx.exe by you ? and what about the missing 500 kb ?

wildweasel wrote:

What's curious is that it's giving you a "File Not Found" error and not a "Bad Command or File Name" error - that tells me that, while DOSBox does acknowledge that the view.exe is there, view.exe is apparently looking for another file entirely before running, and failing to find said file, it quits with a File Not Found error.

That's just my speculation at this point, though - that may or may not be the case.

wildweasel :

well your speculation is really on the money !
If you compare my grabber.jpg with slow_poke's tif you'll see he's missing a bunch of files there. Now he's on Vista, I'm on XP SP2 so it's not quite the same, anyway I have grabber too and it still works for me (like his lookalike utility, pcxdump) for dos screenshot taking.
To be precise, they both work at command prompt, but have always been stuttering from batch scripts under WinXP, but that's another story.

So I have grpcx.exe (that's the one who delivers) and it works.
I have all the other stuff in the directory, I try view.exe and.. it still gives me :
file not found 😵
That really makes me curious, because in my case it shouldn't really be missing whatever other files it's after should it.
So I look up into the documentation (not those *.doc files there for operating info, but the "readme.1st" file instead for, that's right... first instructions) and it says

VIEW.EXE .......... Program that lets you browse documentation files and other text files on your screen. You are using it now to view this file.

Actually, I'm using notepad to read readme.1st now 😜 , but I see your point, go open command window in grabber folder, at prompt, type
view readme.1st
and see attached readme1st.jpg 😎 which proves your point.

Compliments for your perception 😀

Guess the first parameter is the file to view.

Yep. Apparently it worked that way.
It's interesting that at that time they would feel it proper to pack the utility with an internal custom viewer add-in.

Like pcxdump.exe would come with one pcxlab.exe sort of plug in just to be sure you could actually look/browse at all the *.pcx you made.
Otoh, mspaint with Win95 wouldn't open *.pcx anymore, that's vs. Win3.11 like I guess everyone remembers.