Mail Archives: opendos/1997/02/12/05:17:02
On Tue, 11 Feb 1997, Colin W. Glenn wrote:
> > IE: INTEND SPECIAL_FLOPPY1 C:\FLOPPY1
> >
> > Now you've got a different floppy in the A: drive, and your CWD
> > is C:\ and you type CD FLOPPY1, and get a message saying "Please
> > insert SPECIAL_FLOPPY1? Is this your intention? If it is, then
> > it's probably possible, although I doubt it would be very useful.
> > At least I cant see any immediate uses for it.
>
> Creates a 'fake' dir visible in the root, when you UNINTEND it removes the
> fake dir so you won't see it anymore.
>
> And I don't mean to apply this to just floppies, we now have 100+meg
> removable media drives now, not to mention ramcards and the like. Lets
> say you have a file which contains an address book and scheduling calander
> contained on it, you could do the following: (in say AUTOEXEC.BAT)
>
> INTEND Schedule_Card C:\SCHEDULE
> SYMLINK C:\SCHEDULE C:\CALANDER
Sounds like your INTEND command is the same as MOUNT allready is,
just that you must make the dir before you can mount it. In
other words, INTEND == MD \SCHEDULE ; MOUNT A: \SCHEDULE
Could be implemented via an alias or batch file.
> As long as you just _read_ the information in the CALANDER DIR, no errors
> are reported, it's when you run your scheduling software and write the
> updated schedule to its file that the symlink and intend come into play,
> the system sees it as a mirror, it'll prompt you to insert the
> Schedule_Card, (if you hadn't done so already), and update that file as
> well. Hey, cool, you are reminded to keep all copies square even though
> one doesn't really reside permanently on the hard drive.
I'm still not entirely sure what you mean here. I'll explain
MOUNT a little better and you tell me if it is similar to what
you mean.
Make a directory for mounting the disk on
C:\> MD SOMEDISK
Mount the disk
C:\> MOUNT A: C:\SOMEDISK
Access the files from the disk
C:\> DIR SOMEDISK
Unmount the disk when not needed anymore
C:\> UMOUNT \SOMEDISK
Remove the disk
> > > As far as I know, _any_ disk reserves the first sector for the media
> > > information, if not a volume label, then a serial number.
> > Yes, I'm sure that every disk contains a serial number too, but
> > what I'm curious about is HOW to detect a particular filesystem's
> > Do you know how to do it? I'm going to create a bunch of
> > floppies tonight with different filesystems on them (in Linux)
>
> Do a bunch in sequence under one system and see which bytes change.
Yeah, I'm going to try that out, but first I've got to read 1000
manpages. :o)
> > Sure! Why not? Even though I don't have a tape unit, I can see
> > that as a GREAT benifit to those that do.
>
> Well, it would be a GREAT asset, the OS can natively read the tape, no
> special software to run, no different commands to remember, just type:
>
> COPY *.* TAPE:\volumename\*.* /AA-
>
> ie, copy all files with the archive attribute set and reset the bit.
> How easy this would make backups! Could even throw in /S to search all
> subdirectories as well.
Sounds good!
Mike A. Harris | http://blackwidow.saultc.on.ca/~mharris
Computer Consultant | My webpage has moved and my address has changed.
My dynamic address: http://blackwidow.saultc.on.ca/~mharris/ip-address.html
mailto:mharris AT blackwidow DOT saultc DOT on DOT ca
4DOS can be downloaded from ftp://ftp.std.com/vendors/jpsoft
- Raw text -