Oxford Business English International Express Elementary Pdf Printer

First Edition CD-ROM was published by Oxford University Press [OUP], International Computaprint Corp., Bowker, and Tri Star Publishing (Fort Washington, Pennsylvania) as The Oxford English Dictionary Computer File: the Original Oxford English Dictionary on Compact Disc in December 1987 and phased out in December 1992. DOS only, marketed in the U.S.A.

2 CDs and a 5¼ inch floppy. Did not include any material post-1933. 44 million words. ISBN [I’ve never seen it.] Second Edition CD-ROM versions: 1992 - v1 1 CD, 1 diskette. We have surprisingly few Vista reports regarding OED v1.1x. My own installations of v1.10 on 32-bit Vista Ultimate and Home Premium boxes run snappily, both with and sometimes without.

Another user successfully runs v1.10 under the 32-bit Vista Business edition, with Administrator privileges in “Windows XP Compatibility” mode, and launched by (his attempts to launch the OED with the normal OED.EXE executable, or to launch outside XP Compatibility mode, both failed with classic [GPFs].) Another Vista Business user followed these guidelines, but still GPFed because he didn’t have a printer installed. After installing the, OED v1.10 worked. Pressings of OED v3.1 that display a “2004,2005” ( not “2004”) date on the disks work with Vista, and with 64-bit versions of WinXP, if a software patch is downloaded from an OUP website, unZIPped, and applied before a fresh installation of OED v3.1 is run for the first time.

May 28, 2015. The following exercise is taken from the video worksheet that comes with the International Express Teacher's Resource Book DVD. All the worksheets are also. John Hughes examines the case for using graded video in the first of two posts on using video in the Business English classroom. The Power of.

We have confirmation from both OUP and several users that the patch may also be applied in Windows 2000 and 32-bit WinXP (and perhaps in earlier Windows operating systems as well). Moreover, this patch eliminates the 70-90 day revalidation requirement of v3.1! For details, see, below. No reports yet for OED v1.1x. V3.0: C-Dilla apparently will not install on 64-bit machines. OUP’s indefatigable customer support to the rescue: “The OED v3.0 software was not developed to run on Windows 7 and as this version of the OED was discontinued five years ago now, no further development work will be carried out.

Version 3.0 users have the option of upgrading to v4.0.” (Little wonder that infuriated owners of expensive software condescend to warez, e.g. Stripped of C-Dilla!) One cumbersome solution is to install a WinXP child operating system under Virtual PC. Users have had difficulty getting v3.1 to run or even install, due to two very different problems. Again, OUP customer support offered its typical helping hand: “Dear Sir, we do not support betas.

We’re sorry for the inconvenience.” (An understandable posture, which also enables an earlier and longer lunch.) So far, all reports involve users with. In general, apply to Windows 7 as well, with these additional wrinkles. OED won’t run: OED launches, accepts a word look-up, offers several look-up results, but then crashes with, variously, “oed3.exe has stopped working”, “OED CD-ROM Error: Entry cannot be accessed”, and/or “Incompatible Application”. Describes two solutions: not installing the v3.1.1 software patch with “2004,2005” disks; and (contrary to OUP instructions) not rebooting the computer before running the OED for the first time after installation, but instead run the OED once (and perhaps see the wrong fonts), then reboot, then run OED again (and now see the correct fonts). Why this works — who knows.

But two users confirm that it does work. Both users ran as Administrators, and turned off UAC during installation, but were able to run OED subsequently as non-Administrators with UAC.

OED runs but crashes before returning search results: 8/2010: Under 32-bit Win7 Ultimate, v3.1.1 would not run without error until oedcd_v3.exe was launched in Windows XP (Service Pack 3) compatibility mode. UAC was turned off permanently on this machine, which may or may not be a factor.

The result is flawless operation. No other modifications to the user’s normal setup! A simple formula for success, well worth trying before you pull your few remaining hairs out. (Shocked by v4’s inability to save Search results but needing software compatible with Vista Win7, this U.S.-based British user asked OUP Tech Support to swap his old v3.1 Release 1 CDs for overstock v3.1.1 disks. Stonewalled (as usual) by OUP-US in Cary, North Carolina, he then reached a “delightful” woman at OUP-UK who consented to a physical exchange of disks by snail. So miracles do still happen, even at OUP.) Please if you have additional Vista or Windows 7 information to report.

Despite differences in the various OED Second Edition softwares, each individual version is installable, and operable, on almost all Windows 32-bit operating systems: 9x (95, 98, ME) and NT (NT4, 2000, XP, Server — Vista, unfortunately, seems to work out-of-the-box only with OED v1.1x (32-bit machines only), v3.1.1, and v4.0). Often you can buy the OED on,,,,, etc. Or you might near you. English members of 144 libraries that subscribe to a two-year agreement between OUP and the Museums, Libraries, and Archives Council (MLA) can access the OED (and the Oxford Dictionary of National Biography, Oxford Reference Online, Grove Music Online, and Grove Art Online) from any computer at any time, and within the library –. If you want to buy the disk, be wary of imposters like “Concise”, “Compact”, “Mini”, “Shorter”, “Pop-Up”, etc CD versions of Oxford “English Dictionaries” masquerading as the actual OED.

If you want OED version 3.1, don’t buy the “” unless you already own OED version 2 or version 3.0. Instead you want the “Full” version with (very important!) discs labeled “2004,2005” or “2004,2005,2007” (not “2004”) — you may buy it direct from OUP (,, or ). Online stores like and offer much better prices than OUP — look for 25% discounts (). All versions of the OED Second Edition software can, in fact, be installed on a hard disk, notwithstanding the restrictions built into the plain vanilla software of some versions, as detailed above. Root directory — Data File: OED2.DAT635,400,192.

I see no particular advantage to using v1.13, when from OUP. Oed1_14.zip contains a single file, SETUP.EXE. Install v1.14 normally, using SETUP.EXE and the data CD. In retail boxes, SETUP.EXE is provided on a diskette, but it runs equally well from your hard disk — in other words, you do not require an A: diskette drive to install. Then make sure the OED is working properly. Note that there is no copy protection for either the original data CD or for the OED2.DAT dictionary data file; you can simply burn OED2.DAT to the root directory of any CD, and it will run happily — as long as OED2.DAT is on a CD.

If however you want to run v1.13 or v1.14 off hard disk, you must make and mount an, perhaps using and a CD-ROM emulator like. An alternate, light-weight (8Kb device driver + 23Kb control panel) CD-ROM emulator is an unsupported freeware package from Microsoft(!) called, which claims that it requires WinXP Pro or Home, but which works with Win2000 (and maybe other OSes) too.

It supports OED v1.1x, and places very little load on your system (it lacks the robust features of Daemon Tools, but if emulation of an OED v1.1x Data CD is your only requirement, then this is an alternative choice). Beware that this last-named emulator can establish SUBST-like drives on every driveletter below the drive that you pick for your emulated “CD” — and because drives X: Y: or Z: fail due to a, this could involve the pointless allocation of precious resources. The Readme included in the self-extracting ZIPfile explains installation and image file mounting adequately, but fuller instructions are available. In my opinion, Virtual Clone Drive is the better choice. Thanks to William Farrar for this tip.

OED v1.14 contains the same data and executable files as 1.11*, with these exceptions: IPC.DLL is no longer included; UNWISE.EXE is added (used to uninstall the OED application); and three different M$Word macros are also included. During SETUP.EXE installation, when offered the option to install a M$Word macro, skip it (the default action): a is discussed below, and can be downloaded from this website. The 18 True Type fonts of v1.14 (listed below) are different than in v1.10 or v1.11*, and they are automatically copied by SETUP.EXE to [BootDrive]: WINDOWS[ or WINNT] SYSTEM (perhaps the right place for them under Win v3.x, but not the ideal location under Win32 — see further, below). As with v1.10 and v1.11*, install the 18 fonts using Control Panel → Fonts → File → Install New Font (and be sure to check the box “Copy fonts to Font folder” in the “Install New Font” [or “Add Font”] dialog).

You may now run “ /F” against your installation, to confirm that all Files and Fonts are correctly installed and recognized by the operating system. ARBOUP97.TTFArial OUP Bold ARCOUP97.TTFArial OUP Small Caps Regular ARIOUP97.TTFArial OUP Italic AROUP97.TTFArial OUP ARZOUP97.TTFArial OUP Bold Italic HADAS.TTFMonotype Hadassah PI6OUP.TTFPi6OUP MT PI7OUP.TTFPi7OUP MT PI8OUP.TTFPi8OUP MT PI9OUP.TTFPi9OUP MT PLBOUP97.TTFPlantin OUP Bold PLCOUP97.TTFPlantin OUP Small Caps Regular PLIOUP97.TTFPlantin OUP Italic PLOUP97.TTFPlantin OUP PLZOUP97.TTFPlantin OUP Bold Italic PORGRK.TTFPorson Greek OUP One PORGRK2.TTFPorson Greek OUP Two TNRPHON.TTFTimes New Roman Phonetic. An “Image File” (sometimes called an “ISO file”) is an identical copy, in file form, of the physical OED data CD. The following elementary procedure, using excellent freeware (to non-commercial users) tools only, will enable you to operate the dictionary off hard disk with any version of OED v1.1x (v1.10-v1.14). Although unnecessary with v1.10 and v1.11*, some sort of image file procedure is required under v1.13 and v1.14. By far the simplest tool to use to create an image file is the freeware, one of the finest free softwares I’ve ever seen (primarily used for burning CDs and DVDs). Put your OED data CD in your drive, install ImgBurn, run it, and a wizard pops up with six choices: select “Create image file from disc”.

Indicate the “Source” [DVD] drive that contains the CD, indicate a “Destination” filename e.g. OED2.ISO (select a drive: path with plenty of free space! 615Mb will be required), and finally click the disk-to-file graphic at bottom-left. Jump down to “ Fifth”, below.

Here’s the procedure for an older image creation technique. N.B.: the particular imaging tool described below (Mkisofs) is not designed to deal with the additional security and copy protection “features” of OED v2 and v3 (for alternative procedures appropriate to v2 and v3.0, go ). If you’re uncomfortable with command line utilities, you may use many alternative image-making tools to make the ISO file, such as, Nero, Alcohol 120%, etc. Mkisofs.exe -graft-points -v -V OED2 -o E: CDRTOOLS OED.ISO -path-list E: CDRTOOLS OED.LST Mkisofs will rapidly generate an ISO-9660 compliant image file named OED.ISO in E: CDRTOOLS.

Note that buried among the Mkisofs arguments above is an instruction to LABEL the imaged disk “OED2”. If you use a different tool than Mkisofs to create your image file, be sure to LABEL the imaged volume (the image file) “OED2”, because a disk labeled OED2 is one of two methods used by OED.EXE to identify the disk (real or virtual) that contains OED dictionary data. Fifth, install freeware. The word “daemon” means “ server”. Note that although Daemon Tools has long been our preferred CD emulator, Virtual Clone Drive has recently supplanted it.

Note too that version 4 of Daemon Tools includes an optional, and odious, client-side advertising software application called the “Daemon Tools Search Bar” – purportedly bundled with Daemon to defray development costs. Uncheck it at installation time! This is the only opportunity you have to disable this adware, so be vigilant when you install. Alternatively, older does not include adware, and works well with the OED. After you install Virtual Clone Drive or Daemon Tools, reboot and “mount” the OED.ISO image file. [ Mount is a term seldom used by the PC community, but ubiquitous in Unix.

To “mount” a disk or volume (a fixed-size storage space for one or more files) means to somehow connect your computer to the volume data, so that it appears in your computer’s filesystem as a disk (drive) containing one or more directories (“folders”) and files. For what it’s worth, OUP stated ( circa 1998) that v1.0d is “compatible with the CD-ROM extension software shipped with new IIa Macintoshes, including Power Macs For Systems earlier than 7.5 you need the following extensions in your extension folder (found in the system folder): Apple CD-ROM, ISO 9660 Access, and Foreign File Access.

For Systems later than 7.5 you need Apple CD-ROM and Foreign File Access. These extensions must be ‘toggled on’ via the extension manager.” Mac v1.0d presumably has the same feature set as Windows v1.14; and according to an, it also has the same “no hard disk” limitation. “Creating a CD image still works, though With the last few system versions, Apple has provided a utility called Disk Copy that allows one to make a [hard disk] image [file] of any [CD] (with read/write access or read-only, or even compressed). When mounted, the image behaves just like the original [data CD, overriding] copy-protection It does the job. You can make an image of the OED CD-ROM by simply dragging the CD icon from the desktop to the Disk Copy window.

OS 7.5.3 Starter Disk.zip: quadra650.rom: 3. Use Disk Utility to make a 660MB image file. This becomes the new ‘hard disk’. [Edited 2009.12.5] Set up Basilisk II in the Basilisk II Volume settings with the paths to the system software, and the hard disk locations. Set up Basilisk II Memory/Misc ROM File with the path to the ROM. Start Basilisk II and it boots System 7.5.3 off the starter disk in just over 2 seconds. Format the ‘hard disk’.

You can then copy the system folder over to the hard disk and reboot to rid yourself of the starter disk and boot directly off the hard drive. The OSX drive is visible under the name ‘Unix’ and you can drag and drop the OED v1.0d software and OED2.DAT file onto the desktop and drop the fonts in the system fonts folder. Rename the hard disk ‘OED2’, click on the OED2 application, and it’s up and running without problems. It’s very fast and, at 4MB, it’s the smallest way to get OED up and running under OSX Intel.” Basilisk II is fast, but there is one exotic issue ( reported by Darrell Greenwood).

“I am now running Macintosh v1.0d using Basilisk II MacOS on a MacBook Pro 2.8GHz (late 2009, 10.6.2). The emulation opens in a couple of seconds, the app within a second. The load goes from an idle of 6% to 12% while running.

Problem: When OED_Fonts.suit, the 600k TrueType suitcase containing the OED fonts, is put in the System Folder on the Basilik II emulator, it is not recognized or used by the OED app. Cause: There is a big-endian vs. Little-endian byte swapping issue with respect to the change from a Motorola 68000 processor to an Intel x86 processor.

What this means in practice is the Mac file Type code gets its bytes swapped from ‘FFIL’ to ‘LIFF’. When you look at the Type of the suitcase it is ‘FFIL’. When that suitcase is moved to the emulator running on a x86 processor, the processor sees ‘LLIF’ as the type, and doesn’t recognize the font suitcase. Solution: Change the font suitcase Type code from ‘FFIL’ to ‘LIFF’, so that it swaps back to ‘FFIL’. This can be done in numerous ways, e.g. Under OS 7 with, or, under OSX with Terminal, by using the Developer package’s ‘setfile’ command.”.

“A year ago I moved to an Intel Mac from PowerPC, where the [Mac ] OED had been running pretty much constantly in the ‘Classic’ environment under OS X. At first I was unable to use the OED anymore because Apple intentionally did not include a ‘Classic’ environment on Intel versions of OS X. I regained use of the OED with, an open-source ‘hack’ that provides a way to install various ‘Classic’ MacOSes (I used MacOS v9.1) on Intel Macs [ and Linux, BeOS, WindowsNT]. Under Sheepshaver it’s possible to install a whole host of old ‘Classic’ applications.”.

Option 1: OED v1.1x (and v3.x), under Parallels/VMware Fusion All versions of the OED run on all versions of Windows from 95 through XP; OED v1.1x will also run on Windows v3.1. The following table indicates base requirements of several Windows versions. All are clean installs under.

And are other OS X emulation options to explore. If you want to use OED v3.x, then probably go with Windows XP; if you want the smallest possible footprint, then you can’t beat Windows 3.1. (Your other Windows software plans obviously affect your decision.) VMware Fusion v2.0.4 successfully runs OED v1.10 under WinXP if launched with OEDXP.EXE; OED.EXE itself crashes with the usual GPFs.

Operating System Hard Disk OED RAM Windows 3.1 1.4MB v1.10: 600MB 76MB Windows 95 124MB v1.10: 600MB 77MB Windows XP 1.29GB v3.0: 1.6GB 81MB Windows Vista 5.73GB v3.1.1: 1.6GB 553MB Option 2: OED v1.1x under Crossover The OED v1.1x runs under. (v1.13 and v1.14 require that you set up OED2.DAT as a CD drive, real or emulated). Crossover probably will not work with OED v3.x, due to C-Dilla/CD-Cops copy protection. One potential workaround might be to install OED v3.1 under true Windows on a dual-boot Mac machine, and then consult it under OS X. “v1.14 works perfectly under. Here’s what I did: • I am using v3.0.1, which is the commercial version of the free ‘’ program that allows many Windows programs to run under Linux (Word, Quicken, etc). (I just tried the OED under free ‘Wine’ version 20030911, and it appears to work just as well.) • Use Wine to run the v1.14 SETUP.EXE program and install it in the default location.

• Installer exited abnormally, but apparently did the install just fine. • Stick in the CD-ROM, mount it, run OED.EXE, and it works. Additionally, OED will run off of the hard drive directly, if you set up Wine so that a local directory emulates a CD-ROM: • Create directory ~/oed (in your “user” [~] directory, i.e. /home/USERNAME/oed/) • Copy the OED2.DAT file from the CD-ROM to ~/oed/oed2.dat • Tell Wine that ~/oed is a CD-ROM: make this entry in the config file.

By default, OED v1.1x looks for OED2.DAT on the first removable drive; if not found there, an error is declared (e.g. “Cannot read from drive F:” where F: is your first, or only, CD drive). Launch suspends.

This is a watershed moment for many users. They never surmount this hurdle. They’ve already placed the OED data file on ( for example) drive N: (or any drive lettered lower than our hypothetical CD drive F:) — which may be, variously, a second CD DVD drive, or a local or remote hard disk. It would have been less problematic to put the OED on a drive lettered higher than F: (e.g. But they still have options: • Hit “Cancel” (instead of “Abort”), and the OED.EXEcutable will continue to search for a drive with a root directory containing OED2.DAT.

In the cases of v1.10 and v1.11*, both hard and CD drives are searched; in v1.13 and v1.14, only CD drives are searched. • Reassign the driveletter of your CD from “F” to any letter after “N” (if you have Administrator rights under NT4/2000/XP/Vista, open Control Panel → Administrative Tools → Computer Management → Storage → Disk Management → right-click on drive F: → Change Drive Letter and Paths for F:) • Or ( simplest, best, recommended, and often the only effective solution) establish the OED environment variable “OED” (e.g. Using the DOS command “SET OED=N:”; or — recommended! — to establish the variable globally under e.g. Win2000 or XP Pro, open Control Panel → System → Advanced → Environment Variables [in WinXP, this is a small box at the bottom of the Advanced tab] → in System Variables [so that all users have access to it, not just the current user], click New → under “Variable name”, add “ OED” and under “Variable value”, add “ N:”, click OK, and then Reboot.) In formal terms, OED.EXE recognizes two general mechanisms to override the default behavior and “find” the dictionary data on a different drive than the first removable device, whether it be a CD or a hard drive volume. The most reliable pointer for v1.10 and v1.11* is the OED variable. In order of priority, OED.EXE v1.10 v1.11* will.

1) Consult the environment variable OED. “SET OED=d:”, either (local) in an individual DOS session (e.g. “SET OED=N:”), or (global) in the System Environment, thus affecting all sessions. 2) Search local disks for a hard disk or CD labeled “OED2”. Command at DOS “LABEL N:OED2”. Because the original data CD was LABELed “OED2”, the hard disk where OED is relocated should also be LABELed “OED2”. Hard disks should all be lettered higher than (i.e.

Above or before) the first CD drive on your machine. You may use both methods concurrently, for insurance. A network installation may require Method 1). V1.14 reverses the above priority; it cares more about the LABEL on the “CD” (real or virtual) than the OED variable. The “Filename=N: ” spec in the “[data]” stanza of OED.INI is NOT consulted; it simply assists, which obtain DDE (Dynamic Data Exchange) interprocess communication parameters from OED.INI. In other words, OED.INI is not required. If you’re using the actual CD-ROM disk as your dictionary (not a copy on a hard disk), you probably don’t need either of these mechanisms, because OED.EXE will find the CD as long as it is in the first CD drive.

(OED v1.10 and v1.11* will usually find OED2.DAT, either on hard disk or CD, if it is in any local root directory. No assistance from either of these mechanisms is usually required, but if OED generates a “Cannot read from drive d:” error, then set the OED environment variable [Method 1) above].). OED.INI should be located in the DOS Path, normally in%WINDIR% or%SYSTEMROOT% (e.g. C: WINDOWS or C: WINNT).

OED.INI is created by SETUP.EXE, but if you bypass SETUP and manually install the necessary OED files and fonts (which is perfectly acceptable), then you may want to create OED.INI by hand. Again, OED.INI is not required unless you are also using. With any OED v1.x version, employ the OED.INI format required by v1.14 of the software — this affords additional flexibility.

Paste the lines below into file OED.INI, changing only the “Filename=” and the “PathName=” specs to point at your OED EXEcutable installation, and the “Wait=” value to represent the duration of OED initialization on your computer. Note that the “Wait=” duration is machine-dependent: longer for slow machines (5-9 seconds), shorter for fast machines (3-6 seconds). It should roughly correspond to the number of seconds that the blue Oxford shield is displayed when OED.EXE is not cached in machine memory, e.g.

When you run it for the first time in a session (on subsequent launches it will start much faster). [data] Filename=E: [Macro] ExeName=OED.EXE PathName=E: OED ServiceName=OED AppName=Oxford English Dictionary (Second Edition) Wait=4 Adjust the “Filename” variable above to point at the location of OED2.DAT (the dictionary data), on either a CD or Hard drive. Adjust the “ExeName” variable to name the OED executable, usually OED.EXE. Occasionally,, files named STARTOED.BAT or STARTOED.CMD or OEDXP.EXE launch OED.EXE indirectly — if so, use STARTOED.BAT, STARTOED.CMD, or OEDXP.EXE as the “ExeName” instead of OED.EXE.

Adjust the “PathName” variable to point at the directory (folder) of the OED executable OED.EXE. V1.13 and v1.14 + STARTOED [OEDXP] users must also implement procedures described in this “”.

The “ServiceName” and “AppName” should NOT be adjusted — leave as-is. Adjust the optional “Wait” variable to hard code an interval, in seconds, between launch of the OED (when not already running) and passing of the Lookup Word via DDE. The purpose is to prevent an OED crash and possible system lockup if DDE attempts to establish a “channel” before the OED is completely initialized (i.e. While the blue splash screen still displays the Oxford shield). Minimum Wait Time = 1 second (else OED may crash, because DDE can’t yet find OED). Note that does not require OED.INI at all, unless OEDXP is used in conjunction with (called by) a word processing macro.

OEDXP has its own runtime arguments, which replace those in OED.INI. OED.INI is only required by this website’s M$Word, OpenOffice, and WordPerfect word processing macros — otherwise it is not needed. V3.x consumes about 1900MB disk space (roughly triple the 635MB required by OED v1) when run from a hard disk. In its v3.x software series, OUP is trying to reproduce, on local computers, the look-and-feel of the Network OS that it uses in its online OED service. The browser-like interface is very courant, but the cost in efficiency, memory, and disk space is steep. V3.0 and v3.1 (but not v3.1.1) need to be “revalidated” every 70-90 days by inserting the original data CD in the drive, which is a total PITA [discomfort in the hindquarters].

V3.0 requires the presence of Macromedia’s C-Dilla (a.k.a. “SafeCast 2”) copy protection scheme (SafeCast v2.40.11). C-Dilla has been accused of many things (e.g. Being spyware, which is dubious), but it seems to install itself in the low-level boot sectors of your hard disk, where it has been claimed to interfere with multi-booting other operating systems (and interfering with OS/2’s Logical Volume Manager). I know of no way to eliminate the need for C-Dilla to be present when running OED v3.0. If you uninstall C-Dilla and then try to run OED v3.0, the OED automatically reinstalls C-Dilla (without asking permission!) before launching. Conversely, if you uninstall OED v3.0, C-Dilla is not uninstalled too (uninstall with Control Panel → Add/Remove Programs).

Note too that when v3.0 was first published, you needed to be logged on as Administrator just to run OED v3 under Win2000 or WinXP. This requirement has been dropped.

According to OUP, “Local Administrator permissions are no longer required to run the OED as long as the latest version of the authentication process is installed. This can be downloaded from [OUP’s] ” (it amounts to an update to C-Dilla). Lots of other potential v3 snags and snafus are documented by OUP. Here’s how to overcome the 90 day revalidation requirement for v3.0 only (but not v3.1, which beefs up the copy protection by using CD-Cops). First, install v3.0 normally — be sure to tell the OED installer that you will be running the dictionary from CD, not hard disk (a Typical, not Full, setup). Get it working using the physical data CD ( not emulated!).

You must ensure that the OED works normally (the way OUP wants you to use it) before you try to install it to hard disk! But sometimes v3. 21st Century Fox Intro Video Download. 0 won’t work. Take a look at OUP’s. You may see a message similar to this: Or you may get an error message stating that your licence “appears to be broken”. Both are symptoms of an similar to that which can afflict v1.1x — an astonishing lapse in software engineering that has persisted for nearly a decade! Finally, OUP issued (revisions to C-Dilla) that solve the problem for v2 and v3.0 (but are not applicable to v1) (). Read the before installing the new drivers.

These fixes further retard (double or triple) v3.0’s tortoise-like load time, and seem to choke my whole computer (read a pertinent Amazon review entitled — many of these 50+ reviews are interesting); but you can print to your “incompatible printer” directly from the OED after it finally starts running. Note too that OUP has released a rather large bug-fix for v3.0, in two flavors: a for first-time buyers (and for those who upgraded from v1), and a v2-to-v3.0. UnZIP into a temporary directory, run CDSETUP.EXE, and click on “Install”., and install evaluation version 4.x (you can uninstall it as soon as you’re done — but BlindRead and BlindWrite are fine products, and a license only costs USD EUR 39.99).

Make an image of the dictionary CD. The result will be three files, located together in the same hard disk directory, e.g. E: IMAGES OED_CD_3.BWI 789,592,272. E: IMAGES OED_CD_3.B5T 789,592,272.

[FILE_PATHS] CD_PATH=N. If you are or were a v3.0 user, hopefully you upgraded, for reasons that only became compelling in 2007, with v3.1.1. Read on v3.1 was initially released in 2004. In the words of one user, v3.1 added “about 9 new words [to v3.0] as window dressing, ironclad v1.65 copy protection (instead of C-Dilla a.k.a. ‘SafeCast 2’, which is no longer part of the product), and little else” [actually, OUP claims 2000 “new words and phrases”, although I suspect that most are probably modern jargon, i.e. Not words that you ordinarily look up in the OED].

The v3.1 discs were reissued in 2005 as “ Release 2”, reportedly to add a single word that had been inadvertently omitted from the 2004 discs. You can tell which discs you own, because the year of issue is stamped upon them. The most onerous aspect of these releases is the 70-90 day revalidation requirement, inherited from v3.0. CD-Cops completely frustrated revalidation from a CD emulator — you had to carry the data disc with you if you planned to travel for long.

(Note that you can force revalidation, to obtain a fresh 90-day “lease”, by holding down Ctrl-Shift while clicking on the OED shortcut icon.) Release 1 was rife with revalidation errors; OUP had to issue a to fix them. Some users could on certain hardware, or validation simply stopped functioning after a few reauthorizations. They'd reinstall their entire operating system trying to get it to load – a new definition of desperation. Kapersky and Norton AV sometimes blocked it. Convey the rich flavor of these experiences, along with the nightmare that OUP calls “Tech Support”.

Then, in early 2007, OUP issued a software patch called “ v3.1.1”, which confers two big benefits: it eliminates the 70-90 day revalidation requirement under “Windows 98SE, ME, NT4, 2000, and XP”; and it enables v3.1 under both 32- and 64-bit versions of Vista and 64-bit versions of XP. Owners of Release 2 v3.1 discs dated “2004,2005” (not “2004”) with key numbers FT39P-9UFX-L92Q or URAP9-Z2M9-R6EH only (these two keys seem to apply to most, maybe even all, of these discs) may (read the before applying the patch, and authenticate with your key number translated to lower case and no hyphens, i.e. Ft39p9ufxl92q or urap9z2m9r6eh); otherwise obtain v3.1.1 by contacting. Owners of v3.1 discs dated “2004” are (or were) invited to return them to OUP Tech Support, in exchange for “Full” Version 2005 discs, to which the patch can then be applied (after uninstalling the 2004 version, and performing a “Full”, not “Typical”, reinstallation), or for newly remastered 2007 discs.

Briefly, in March 2007, the said: “If your OED v3.1 CDs do not show the date 2005, then you can exchange them for the OED v3.1 Release II free of charge, on receipt of the old ones. Please send CDs to Technical Support with your name and address and the reason why you are sending them.” You may need to reinstall from scratch: instructions that accompanied one early set of disks required that this patch be applied before first use, and before entering the authentication code (supplied in a letter from OUP — you must contact OUP directly to obtain the code unless your key number, a.k.a. Authentication/validation code, is one of the two numbers mentioned above); however, the current online instructions suggest that the OED may already be installed and running, and therefore reinstallation should be unnecessary (indeed, a newer version of the patch has been posted). All this complication seemed to arise as an interim emergency measure under the pressure of frustrated Vista users. Remastered disks of v3.1.1 dated 2007 incorporated these changes and obviated the need to apply any patch. V3.1.1 also upgraded CD-Cops to v1.71. Altogether, v3.1.1 represented a rebirth of trust & openness at OUP: v3.1.1 was the first version of the OED since v1.11* (anno 1995) that could be freely installed on a hard disk without further hindrance.

It works as advertised. Kudos to OUP, for restoring some sanity to their marketing. OUP appeared to be endeavoring to repair a battered reputation, to be reaching out generously to its customers at real cost in time, trouble, and money.

V3.1.1 presaged the U-turn in DRM policy that emerged more clearly (if not quite completely) in v4 The net result of v3.1.1 is software that works without annoyance. It isn’t particularly fast, and the interface is clumsy. But it’s the OED nonetheless — and you can install it on your hard disk. Note that v3 will crash and ask you to reinstall the software(!) for the trivial reason that OED.INI (which resides in%SYSTEMROOT% or%windir%, e.g.

C: WINDOWS) is missing. This might happen if you overwrite OED.INI because you also run other versions of the OED, or if you aren’t privileged to write to%SYSTEMROOT%.

Just use a plain-vanilla generic OED.INI to avoid this herculean task, with its array of CDs, verification, and what-not, then fine-tune the various options after you’re up and running. Something like this will suffice (set both [FILE PATHS] specs to the uppermost OED directory). States that “two of my customers have told me that [they] were able to get OED version 3.0 to run on a Mac using Microsoft’s product. In fact they both told me they got it to work without any special settings and the installation was easy.” An OSX user writes (11/2006): “I just installed v3.0 onto a MacBook Pro (via [with] Safedisk emulation checked, after applying Safedisc2Cleaner v1.20 to the SCRfrsh.exe infection) running Windows XP on. It works well.

A Windows ‘print to pdf’ program delivers results to my OSX desktop via the OED ‘Print’ command.” Another OSX user writes (4/2007): “I installed v3.1 [Release 2 dated 2005] in on machines configured with Windows XP and Windows Vista, and immediately ran the. I was asked to enter my CD-ROM sticker number, and everything works. This is great. No need for dual boot.” The same user also experimented with Apple’s. He installed OED v3.1 Release 2 (using 2005 disks) under Windows Vista, and then applied the 2007 v3.1.1 software patch.

“Everything works, as expected.” Another OSX user was upgraded for free from v3.0 after complaining to OUP-US Customer Service about authentication problems: “ v3.1.1 (2007 disks) works very nicely on my Apple Powerbook, running Windows XP Professional via BootCamp.” A Linux user, who for five years(!) had been trying to get various iterations of v3.x to run under SuSE and openSuSE, finally succeeded (2/2008) with OED v3.1.1 and 32-bit. “I just used the technique of exhaustion: if at first it doesn’t work, do it again (and again, and again) in a different order, and hope for the best.

Eventually, it worked.” To no avail, he had tried “Win4Lin, VMWare, Xen, CrossOverOffice, and Wine, repeating with each new release of SuSE, plus Mandrake/Mandriva and other Linux flavours.” Success came at last with, a free Innotek product installed with openSuSE’s built-in YaST installation tool, hosting a WinXP Pro virtual machine. “It should work — provided VirtualBox is installed correctly. VirtualBox only worked for me when the kernel-source and kernel-syms packages had been pre-installed with YaST before VirtualBox. ( kernel-source and kernel-syms are not VirtualBox packages. YaST can find and install them, provided the appropriate repositories have been enabled. These can be found and enabled by following these and doing what Jem Matzan says in the paragraphs ‘Adding sources to YaST’ and ‘Adding repo addresses’ – making sure that the openSuSE build service for VirtualBox repository is checked and added to the list.

Accept and when prompted trust and import the key. Then it should all go OK.) “When installing the WinXP Virtual Machine, I accepted all the defaults offered by VirtualBox. WinXP runs happily in 192MB allocated base memory. “This is a ‘Full’ OED install, running without the Data CD in the drive. Speed is excellent (after the usual slow start). Typefaces are perfectly readable (though not perfect).

When installing [OED v3.1.1 in the WinXP VM], first mount CD/DVD ROM from the ‘Devices’ menu in the Virtual Machine, then installation should proceed normally. When prompted for the Data Disc, remove the installation disc, unmount CD/DVD from the ‘Devices’ menu in the Virtual Machine, then insert the data disc and remount CD/DVD ROM. Do the same when prompted for the discs by CD-Cops.”. The good news about version 4, released in May 2009, is that it installs to the hard disk and does not require periodic “verification”; and that there’s a native version for Macintosh OS X (but not for Linux or mobile devices — although, as usual, there’s a satisfactory ). The bad news is that the Upgrade edition is Windows-only (the Full v4.0 version includes both Windows and Mac software), and moreover you can no longer Upgrade from either the Windows or the Macintosh releases of OED version 1, but only from Windows version 2 and up (for £78 US$79.95 ¥15,000 from OUP, $63.72 at or about £39 – that’s half off the U.K. MSRP/RRP; note the incongruous £ $ pricing from OUP itself).

Inter alia, this change of policy means that Mac users who bought the Mac version of OED v1 (for an astronomical price if you were an early purchaser) and have since jumped through formidable technical hoops to run the OED on their PPC and Intel Macs, are now being punished for OUP’s lengthy interval of neglect, and must purchase the Full version once again (for £169.57+VAT US$295 ¥40,000 MSRP) to obtain the first native Mac OED software since v1.0d. According to a U.S.-based customer service rep, this was a “marketing decision” and there is “no leniency”. However, on 6 January 2009, quoted a recently-received message from OUP: “Registered Users of the Version 1.0d Mac software such as yourself will be entitled to purchase this software for £127.17 plus VAT and £3.00 postage.

This price includes a 25% discount off the standard price of £169.57 plus VAT and postage.” Moreover, several Europe-based OED users speaking by phone with U.K. Customer service have successfully argued that they should not be obliged to purchase a Full version twice for (loosely-speaking) the same operating system; they have been sent the Full version at the Upgrade price. And a states that Mac v1 users with proof of purchase may upgrade, apparently for ¥13,500.

There is no mention of these ‘accommodations’ to old users on the U.K. Website — indeed, as of 15 August 2009, the Windows v4 Upgrade CD is no longer mentioned or offered for sale there! Where did it go?

(A few independent U. Atlas Des Amphibians De Guyane Pdf File here. K. Web booksellers do offer it – but for around £122, a veritable import price.) These confusing disparities in policy, pricing, availability, and conduct will be to a host of (especially North American) users (one particularly irate user “”), but a potential opportunity for others.

(: “I got a mailshot telling me that as a registered user of an older version, I could get the new one for £78. I placed my order immediately The mailshot didn’t mention that the upgrade was Windows only, it was only the order acknowledgement email that admitted that, so I complained, and the nice people at the OED very kindly offered to send me the full product at the upgrade price As I mentioned to them, there are potentially a lot of their customers who want to switch from Windows to Mac. Don’t know why their US branch should be less helpful.”) Technical Requirements (per ).