Xref: utzoo alt.msdos.programmer:2545 comp.sys.ibm.pc.misc:8435 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!samsung!news.cs.indiana.edu!ux1.cso.uiuc.edu!news.iastate.edu!cs352a41 From: cs352a41@cs.iastate.edu (Adam Goldberg) Newsgroups: alt.msdos.programmer,comp.sys.ibm.pc.misc,aus.computers.ibm-pc Subject: Re: Setting the Turbo mode by software Message-ID: Date: 10 Apr 91 15:15:45 GMT References: <1991Apr10.104737.9962@cc.newcastle.edu.au> Sender: news@news.iastate.edu (USENET News System) Organization: Iowa State University, Ames IA Lines: 26 eepjm@cc.newcastle.edu.au writes: >How does one tell MS-DOS that it's in-memory copies of a disk FAT and >directory are invalid - i.e. how can one force it to re-read the disk rather >than rely on its obsolete in-memory copy? Re-booting the machine works >(but by then it's usually too late, another disk-full of vital files has >been corrupted), but I'd like to have a less drastic solution. >Peter Moylan eepjm@cc.newcastle.edu.au MS-DOS sends a message to the device driver for that paricular device, the device driver is either able (through hardware, disk serial#, drive door open, or some such device) tell if the disk has been changed. The device driver either sends back "Yes, it has been changed", "No, it hasn't", or "Aw, heck, how the h**l am I supposed to know?". I know this isn't as complete as you'd like, Peter, but the hardware-stuff seems like it would be pretty specific to the drive, dos, device driver, etc. Adam -- +-----------------------------------------------------------------------------+ ! Adam Goldberg ! "Working to make EMACS safe for mankind" ! ! cs352@zaphod.cs.iastate.edu ! "It's simple! Even a PASCAL programmer could ! ! tabu6@ccvax.iastate.edu ! do it!" !