Care, and it may have an undelete deal. You can likely undelete stuff if in something like Windows Explorer, but I don't think that's possible if you delete it from a command prompt.
Deleting files works the same way whether you delete from Windows Explorer or N>the command prompt. It has to do with the filesystem, not the user interface N>you're using.
Well, I've tried an undelete utility after zapping stuff from a DOS prompt, and it didn't work.
Care, and it may have an undelete deal. You can likely undelete stuff if in something like Windows Explorer, but I don't think that's possible if you delete it from a command prompt.
Deleting files works the same way whether you delete from Windows Explorer or N>the command prompt. It has to do with the filesystem, not the user interface N>you're using.
Well, I've tried an undelete utility after zapping stuff from a DOS prompt, and it didn't work.
Daryl Stout wrote to NIGHTFOX <=-
Well, I've tried an undelete utility after zapping stuff from a DOS prompt, and it didn't work.
Well, I've tried an undelete utility after zapping stuff from a DOS
prompt, and it didn't work.
Yeah no guarantees, because once a file is deleted, the diskspace is freed and something can come along and use that space.
Nightfox wrote to Tony Langdon <=-
Back in the day, when using MS-DOS or similar DOS operating system, you could easily undelete a file immediately after deleting it because
there was nothing going on that would use that file's space. But with Windows and other modern operating systems, there are background tasks that could potentially write something where the deleted files used to
be.
By "DOS prompt", do you mean you were using MS-DOS (or similar DOS), or do yo N>mean the command prompt in Windows? If this was in Windows, you need to run N>the undelete utility fairly quickly because with the background tasks Windows N>does, Windows could overwrite the deleted file's sectors, making them unable N>be recovered.
Yep, it was easier in the DOS days, because the probability of something TL>writing all over the disk before you attempted to unerase something was much TL>lower. It would only be if you were running Windows (3.x), DESQview or sele TL>TSRs that you might have a problem, and the first 2 were easy to shut down.
Daryl Stout wrote to TONY LANGDON <=-
That brings back memories...Windows 3.11 and DESQview with
QEMM...wow!!
That brings back memories...Windows 3.11 and DESQview with
QEMM...wow!!
Daryl Stout wrote to Tony Langdon <=-
To me, DESQView and QEMM were great for running GT Power under
dial-up, and it allowed me to do stuff in the background, while the BBS was running. I think Quarterdeck Software, who made QEMM and DESQview,
has long since gone out of business.
To me, DESQView and QEMM were great for running GT Power under dial-up, and it allowed me to do stuff in the background, while the BBS was running. I think Quarterdeck Software, who made QEMM and DESQview, has long since gone out of business.
Yeah, guess OS/2, Windows and later, Linux kinda killed off their market. :(
Daryl Stout wrote to TONY LANGDON <=-
I used to joke that those who use Linux "have a fetish for penguins".
You're just jealous you don't have penguins living naturally on your side of TL>the equator. :P
Daryl Stout wrote to TONY LANGDON <=-f
You're just jealous you don't have penguins living naturally on your side
the equator. :P
They're just birds wearing tuxedos. <G>
You're just jealous you don't have penguins living naturally on your sidef
the equator. :P
They're just birds wearing tuxedos. <G>
| Sysop: | Ragnarok |
|---|---|
| Location: | Dock Sud, Bs As, Argentina |
| Users: | 136 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 31:35:57 |
| Calls: | 15,172 |
| Calls today: | 1 |
| Files: | 19,859 |
| D/L today: |
18 files (4,249K bytes) |
| Messages: | 1,692,585 |