List Archives >  Procite List Archive >  Archive by date >  This Month By Date >  This Month By Topic

Re: Exit to DOS

Search email archive for  

Re: Exit to DOS
Author: Larry Greenwood L 857-3200    Posted: Wed, 11 Sep 1996 10:42:13 +22310
Date: Wed, 11 Sep 1996 10:42:13 +22310718 Reply-To: PRO-CITE The Personal Bibliographic Software Discussion List Sender: PRO-CITE The Personal Bibliographic Software Discussion List From: Larry Greenwood L 857-3200 Subject: Re: Exit to DOS In-Reply-To: On the issue of "Exit to Dos". Try executing the procite start command from the autoexec.bat file with a "call" command. Following the call command type "procite" or whatever command starts procite. Examples below. call procite procite Upon exiting from dos the procite start command would be automatically issued. This may work. Larry Greenwood MSU Library On Wed, 11 Sep 1996, Pam Hystad wrote: > Debra, > > We never found a way to prevent that situation from the Pro-Cite end either (or > from many other network apps) which is one of the reasons my sys admin guy is so > "permissions-sensitive" at the network level. We're running a DEC (Pathworks -- > LanManager) network, and no-one can access shared resources without logging on > with a valid username and password. Then permissions to various drives and dirs > can be granted by username (this is the readers digest condensed version 8^) ). > > Another MAJOR problem we had with that "DOS Exit" was that apparently memory > allocated to hold on to Pro-Cite while the user shelled out to DOS and back, was > not released after returning to Pro-Cite, but was held until the user completely > closed and exited the Pro-Cite session -- caused us some big headaches for a > while.... > > Pam Hystad > Sys Dev Spec > CDSI for USEPA

Re: Exit to DOS
Author: Larry Greenwood L 857-3200    Posted: Thu, 12 Sep 1996 15:04:06 +22310
Date: Thu, 12 Sep 1996 15:04:06 +22310718 Reply-To: PRO-CITE The Personal Bibliographic Software Discussion List Sender: PRO-CITE The Personal Bibliographic Software Discussion List From: Larry Greenwood L 857-3200 Subject: Re: Exit to DOS In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII You are right. But what about the following: call pro.bat process where pro.bat is procite.exe I don't have a copy to try out. If not then I confess I dont know what I am talking about! Larry. On Wed, 11 Sep 1996, Pam Hystad wrote: > Larry, > > AFAIK (as far as I know) the CALL command only works with ".bat" files, not > ".exe" files -- but even if you wrote a .bat to start Pro-Cite, putting a "call" > command in your autoexec.bat would just load Pro-Cite every time you booted the > PC, and have no impact on the Pro-Cite function, "Exit to DOS". > > Pam Hystad > Sys Dev Spec > CDSI for USEPA

Re: Exit to DOS
Author: Pam Hystad    Posted: Wed, 11 Sep 1996 10:06:06 -0500
Date: Wed, 11 Sep 1996 10:06:06 -0500 Reply-To: PRO-CITE The Personal Bibliographic Software Discussion List Sender: PRO-CITE The Personal Bibliographic Software Discussion List From: Pam Hystad Subject: Re: Exit to DOS In-Reply-To: Your message of "Wed, 11 Sep 96 00:01:14 EDT." <Pine.GSO.3.95.960910235504.1500D-100000@ns> Debra, We never found a way to prevent that situation from the Pro-Cite end either (or from many other network apps) which is one of the reasons my sys admin guy is so "permissions-sensitive" at the network level. We're running a DEC (Pathworks -- LanManager) network, and no-one can access shared resources without logging on with a valid username and password. Then permissions to various drives and dirs can be granted by username (this is the readers digest condensed version 8^) ). Another MAJOR problem we had with that "DOS Exit" was that apparently memory allocated to hold on to Pro-Cite while the user shelled out to DOS and back, was not released after returning to Pro-Cite, but was held until the user completely closed and exited the Pro-Cite session -- caused us some big headaches for a while.... Pam Hystad Sys Dev Spec CDSI for USEPA

Re: Exit to DOS
Author: Pam Hystad    Posted: Wed, 11 Sep 1996 16:00:00 -0500
Date: Wed, 11 Sep 1996 16:00:00 -0500 Reply-To: PRO-CITE The Personal Bibliographic Software Discussion List Sender: PRO-CITE The Personal Bibliographic Software Discussion List From: Pam Hystad Subject: Re: Exit to DOS In-Reply-To: Your message of "Wed, 11 Sep 96 10:42:13." Larry, AFAIK (as far as I know) the CALL command only works with ".bat" files, not ".exe" files -- but even if you wrote a .bat to start Pro-Cite, putting a "call" command in your autoexec.bat would just load Pro-Cite every time you booted the PC, and have no impact on the Pro-Cite function, "Exit to DOS". Pam Hystad Sys Dev Spec CDSI for USEPA

Re: Exit to DOS
Author: Pam Hystad    Posted: Fri, 13 Sep 1996 09:43:40 -0500
Date: Fri, 13 Sep 1996 09:43:40 -0500 Reply-To: PRO-CITE The Personal Bibliographic Software Discussion List Sender: PRO-CITE The Personal Bibliographic Software Discussion List From: Pam Hystad Subject: Re: Exit to DOS In-Reply-To: Your message of "Thu, 12 Sep 96 15:04:06." Hi Larry, It was my impression that the original poster was concerned about people using Pro-Cite to connect to network drives, and then using the Pro-Cite function "Exit to DOS" to go prowling around on network drives that they ordinarily wouldn't have access to. I may have made that assumption <because> we have some users tricky enough to try this! The bottom line is, the only thing accomplished by calling Pro-Cite from the autoexec.bat would be to load Pro-Cite at every boot-up, and would have no impact at all on the "Exit to DOS" function inside of Pro-Cite, since control isn't really returned to DOS by that function, it's just a shell-out. Sorry if we misunderstood each other, Pam

Re: Exit to DOS
Author: Debra Rand    Posted: Sun, 15 Sep 1996 22:07:07 -0400
Date: Sun, 15 Sep 1996 22:07:07 -0400 Reply-To: PRO-CITE The Personal Bibliographic Software Discussion List Sender: PRO-CITE The Personal Bibliographic Software Discussion List From: Debra Rand Subject: Re: Exit to DOS In-Reply-To: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII I am the original poster on this question and Pam has the problem correctly stated. Proc-Cite is a choice off of our menu of databases. So far, no one has done any damage by using the Exit to DOS shell. However, we consider it a security problem and have not broadly encouraged use of the software outside of library staff. The library produces several databases with Pro-Cite including our institution's faculty publications list which we wanted to make widely available over the library's network. Debra Rand e-mail: Health Sciences Library Director fax: 718-470-6150 Long Island Jewish Medical Center voice: 718-470-7070 New Hyde Park, NY 11040 On Fri, 13 Sep 1996, Pam Hystad wrote: > Hi Larry, > > It was my impression that the original poster was concerned about people using > Pro-Cite to connect to network drives, and then using the Pro-Cite function > "Exit to DOS" to go prowling around on network drives that they ordinarily > wouldn't have access to. I may have made that assumption <because> we have some > users tricky enough to try this! > > The bottom line is, the only thing accomplished by calling Pro-Cite from the > autoexec.bat would be to load Pro-Cite at every boot-up, and would have no > impact at all on the "Exit to DOS" function inside of Pro-Cite, since control > isn't really returned to DOS by that function, it's just a shell-out. > > Sorry if we misunderstood each other, > > Pam >

Re: Exit to DOS
Author: Pam Hystad    Posted: Mon, 16 Sep 1996 09:51:56 -0500
Date: Mon, 16 Sep 1996 09:51:56 -0500 Reply-To: PRO-CITE The Personal Bibliographic Software Discussion List Sender: PRO-CITE The Personal Bibliographic Software Discussion List From: Pam Hystad Subject: Re: Exit to DOS In-Reply-To: Your message of "Sun, 15 Sep 96 22:07:07 EDT." <Pine.GSO.3.95.960915220149.5648B-100000@ns> Hi Debra, Usually only the network / system administrator can limit or grant the various permissions to shared resources. Each type of network has its own little quirks, so I wouldn't want to steer you wrong with the way we work it here 8^)! I believe we DO grant all permissions to the Pro-Cite drive, its root dir, and the styles and template dirs, to a pretty large group of usernames (but not ALL users).In addition, individual dirs for specific datasets are further limited to certain usernames, and non-Pro-Cite drives and dirs have username-specific grants of permissions too. Our sysadmin is a true obsessive-paranoid, but I guess that's what you need for a secure network! HTH, Pam

Previous by date: Is Windows ProCite fatally flawed, Andy Toth
Next by date: Re: Exit to DOS, Larry Greenwood L 857-3200
Previous thread: HealthStar & Procite, Jim Morgan
Next thread: Re: Exit to DOS, Larry Greenwood L 857-3200