While multiple versions of GraphicsMagick may be installed at one time, if your intention is to replace a prior installation of GraphicsMagick with a newer version, then it is wise to uninstall the existing GraphicsMagick (see uninstall procedure) prior to installing the newer version. While it is not a requirement, it is strongly recommended that the package (GraphicsMagick is tested with version 9.10) be installed. GraphicsMagick uses Ghostscript to render Postscript and PDF files, as well as formats where a translator to Postscript is available. GraphicsMagick will use the to support the standard set of Adobe Postscript fonts like 'Helvetica' and 'Times Roman' if these fonts are not available as TrueType fonts.
The Ghostscript fonts need to manually installed with administrator privileges in the Ghostscript installation directory. Make sure to install a Ghostscript which is compatible with the GraphicsMagick you are installing.
For example, if you are installing a 64-bit GraphicsMagick, you should install a 64-bit Ghostscript. The installation order of the two packages is not important. Both 32 and 64-bit versions of GraphicsMagick and Ghostscript may be installed at the same time. Retrieve the GraphicsMagick Windows binary install package from a one of the ftp sites listed at the page. The available install packages are as follows Windows Dynamic-Multithread (DLL-based) install package with utilities, ImageMagickObject COM object, and web pages: GraphicsMagick-1.3-Q8-win32-dll.exe GraphicsMagick-1.3-Q16-win32-dll.exe GraphicsMagick-1.3-Q8-win64-dll.exe GraphicsMagick-1.3-Q16-win64-dll.exe Note that the QuantumDepth=8 version (Q8) which provides industry standard 24/32 bit pixels consumes half the memory and about 30% less CPU than the QuantumDepth=16 version (Q16) which provides 48/64 bit pixels for high-resolution color.
A Q8 version is fine for processing typical photos intended for viewing on a computer screen. If you are dealing with film, scientific, or medical images, use ICC color profiles, or deal with images that have limited contrast, then the Q16 version is recommended. The win32' packages are for 32-bit or 64-bit Windows, whereas the `win64 packages are only for 64-bit Windows. The 64-bit version allows processing larger images in memory (rather than disk files), provided that the system has more than 2GB of RAM installed. Memory access is 1000 times faster than disk access. A screen is displayed which presents most (or all) of the following options:. Create a desktop icon.
Update executable search path. Associate supported file extensions with GraphicsMagick. Install ImageMagickObject OLE Control for VBscript, Visual Basic, and WSH. 'Creating a desktop icon' and 'Update the executable search path' are selected by default. The remaining options default to un-selected. Select the options you prefer. Think twice before selecting ' Associate supported file extensions with GraphicsMagick' since this will set up approximately fifty file associations, including common formats like JPEG, GIF, PNG, TIFF, and PDF.
These file associations will be to the 'gmdisplay' program which is suitable for displaying images, but currently offers little more than that. Windows XP seems to handle the file associations pretty well, allowing you to choose from a list of programs, but older systems like Windows NT 4.0 and Windows '98 only support a single association per format, which can be quite annoying.
Associations for GraphicsMagick's native formats (such as ) will always be made. Once you have made your selections, click on ' Next' to continue. The GraphicsMagick package incorporates its own uninstall functionality. Always remove an installed GraphicsMagick via its uninstall function since manually removing it (such as by removing its installation directory) will leave behind the registry entries and path settings established at install time.
Under Windows '95 and Windows '98, use the ' Uninstall' entry in the GraphicsMagick portion of the Windows start menu to initiate the uninstall. On NT 4.0 and 5.X -based systems, GraphicsMagick should be removed via the ' Add or Remove Programs' area of the Windows Control Panel. Select the GraphicsMagick package from the list, and click on ' Change/Remove' to uninstall it. The GraphicsMagick gm utility may be executed as a sub-process by other programs. If gm utility is not in the systems executable search path (it should be since the GraphicsMagick install extends the path), then the utility should be executed via the complete path to the executable.
The COM object may be used to execute the gm sub-functions (e.g. 'convert') without spawning a new process or causing Windows to pop up a window. The COM object supports multi-threaded concurrent use. When GraphicsMagick is installed, entries are added to the Windows Registry so that other programs may obtain information regarding the most recently installed GraphicsMagick. These entries are available under the registry path HKEYLOCALMACHINE SOFTWARE GraphicsMagick Current.
These registry keys are currently available: Key Name Key Type Description BinPath REGSZ Directory where GraphicsMagick executables are installed ConfigurePath REGSZ Directory where configuration files are installed LibPath REGSZ Directory where GraphicsMagick core DLLs are installed CoderModulesPath REGSZ Directory where GraphicsMagick loadable coder modules are installed FilterModulesPath REGSZ Directory where GraphicsMagick loadable filter modules are installed SharePath REGSZ Directory where configuration files are installed. The Visual C distribution targeted at Windows 2000 through Windows 8 does not provide any stock workspace (DSW) or project files (DSP) except for those included with third party libraries. Instead, there is a 'configure' program that must run to create build environments to satisfy various requirements. The configure program resides in VisualMagickconfigure in the GraphicsMagick source tree. A pre-compiled configure.exe is provided, as well as Visual Studio project files to recompile it from source code if needed. Once started, the configure program provides this configuration dialog after proceeding past the initial notifications screen: In addition to (or as a replacement to) the above dialog, the configure.exe program supports these command-line options: /Q8 /Q16 /Q32 Set quantum depth /x64 Add x64 configuration /mtd /sts /mts /mtsd Set project type /noWizard Do not show the wizard /openMP Enable openMP The Visual C system provides three different types of 'runtimes' that must match across all application, library, and DLL code that is built. The 'configure' program creates a set of build files that are consistent for a specific runtime selection.
The three options for runtime support are:. Dynamic Multi-threaded DLL runtimes (VisualDynamicMT), /mtd option. Static Single-threaded runtimes ( VisualStaticST), /sts option. Static Multi-threaded runtimes (VisualStaticMT), /mts option. Static Multi-threaded DLL runtimes (VisualStaticMTDLL), /mtsd option In addition to these runtimes, the VisualMagick build environment allows you to select whether to include the X11 libraries in the build or not.
X11 DLLs and headers are provided with the VisualMagick build environment. Most Windows users do not use X11 so they will prefer to build without X11 support.
When X11 is not supported, gm subcommands 'animate', 'display', and 'import' will not work. This leads to five different possible build options, which should cover almost any particular situation. The default binary distribution is built using #1 from above with the X11 libraries excluded. This results build using all DLL's for everything and multi-threaded support (the only option for DLL's). To do a build for your requirements, simply go to the configure sub- directory under VisualMagick and open the configure.dsw workspace (for Visual C 6.0) or configure.sln (for Visual C 7.X or 8.X). Set the build configuration to 'Release' under the 'Build., Set Active Configuration.'
Build and execute the configure program and follow the on-screen instructions. You should not change any of the defaults unless you have a specific reason to do so. The configure program provides a button entitled Edit 'magickconfig.h' Clicking this button brings up magickconfig.h in Windows notepad for optionally changing any preprocessor defines in GraphicsMagick's magickconfig.h file. This file is copied to magick magickconfig.h.
You may safely open magick magickconfig.h, modify it, and recompile without re-running the configure program. In fact, using Visual Studio to edit the copied file may be preferable since it preserves the original magickconfig.h file. Key user tunables in magickconfig.h include: QuantumDepth (default 8) Specify size of PixelPacket color Quantums (8, 16, or 32) A value of 8 uses half the memory than 16 and may run 30% faster, but provides 256 times less color resolution than a value of 16. UseInstalledMagick (default undefined) Define to build a GraphicsMagick which uses registry settings or embedded paths to locate installed components (coder modules and configuration files).
The default is to look for all files in the same directory as the executable. ProvideDllMain (default undefined) Define to include a DllMain function ensures that the GraphicsMagick DLL is properly initialized without participation from dependent applications. This avoids the requirement to invoke IntializeMagick from dependent applications but only works for DLL builds.
EnableBrokenCoders (default undefined) Define to enable broken/dangerous file format support. Only enable this if you have complete control over the input files and not for arbitrary files such as uploaded from untrusted sources via the Internet.
Currently this must be enabled to enable Adobe Photoshop Format (PSD). After creating your build environment you can proceed to open the DSW (or SLN) file that was generated in the VisualMagick directory and build everything from there. In the final DSW file you will find a project call 'All'. In order to build everything in the distribution, select this project and make it the 'active' project. Set the build configuration to the desired one (Debug, or Release) and do a 'clean' followed by a 'build'. You should do the build in a specific way:. Make the 'All' project the active project (Bold) Right click on the All project and select 'Set As Active Project'.
Select 'Build., Clean'. Select 'Build., Build'. Go get some coffee unless you have a very fast machine! The 'Clean' step is needed in order to make sure that all of the target support libraries are updated with any patches needed to get them to compile properly under Visual C. All of the required files that are needed to run any of the command line tools will be found in the 'bin' subdirectory of the VisualMagick subdirectory. This includes EXE, and DLL files. You should be able to test the build directly from this directory without having to move anything to any of the global SYSTEM or SYSTEM32 areas in the operating system installation.
Note #1: The Visual C distribution of GraphicsMagick comes with the Magick C wrapper by default. This add-on layer has a large number of demo and test files that can be found in GraphicsMagick Magick demo, and GraphicsMagick Magick tests. There are also a variety of tests that use the straight C API as well in GraphicsMagick tests. All of these programs are NOT configured to be built in the default workspace created by the configure program. You can cause all of these demos and test programs to be built by checking the box in configure that says: 'Include all demo and test programs' In addition, there is another related checkbox (checked by default) that causes all generated project files to be created standalone so that they can be copied to other areas of you system. This is the checkbox: 'Generate all utility projects with full paths rather then relative paths' WOW - that a mouthfull - eh?
Visual C uses a concept of 'dependencies' that tell it what other components need to be build when a particular project is being build. This mechanism is also used to ensure that components link properly.
In my normal development environment, I want to be able to make changes and debug the system as a whole, so I like and NEED to use dependencies. However, most end users don't want to work this way. Instead they really just want to build the package and then get down to business working on their application. The solution is to make all the utility projects (UTILxxxxyyexe.dsp) use full absolute paths to all the things they need. This way the projects stand on their own and can actually be copied and used as templates to get a particular custom application compiling with little effort.
With this feature enabled, you should be able to nab a copy of. VisualMagick utilities UTILgmxxxexe.dsp (for C) -or- VisualMagick Magick demo UTILdemoxxxexe.dsp (for C).
And pop it into notepad, modify it (carefully) to your needs and be on your way to happy compiling and linking. You can feel free to pick any of the standard utilities, tests, or demo programs as the basis for a new program by copying the project and the source and hacking away. The choice of what to use as a starting point is very easy.
You can use the 'System' control panel to allow you to add and delete what is in any of the environment variables. You can even have user specific environment variables if you wish. PATH This sets the default list of places were Windows looks for EXE's and DLL's.
Windows CMD shell seems to look in the 'current' directory first - no matter what, which may make it unnecessary to update the PATH. If you wish to run any of utilities from another location then you must add the path to your 'bin' directory in. For instance, you might add: D: Devel GraphicsMagick VisualMagick bin to do this for the default build environment like I do. MAGICKHOME If all you do is modify the PATH variable, the first problem you will run into is that GraphicsMagick may not be able to find any of its 'modules.
![]()
Modules are all the IMMOD.DLL files you see in the distribution. There is one of these for each and every file format that GraphicsMagick supports. This environment variable tells the system were to look for these DLL's. The compiled in 'default' is 'execution path' - which says - look in the same place that the application is running 'in'. If you are running from somewhere other then 'bin' - this will no longer work and you must use this variable. If you elect to leave the modules in the same place as the EXE's (a good idea) then you can simply set this to the same place as you did the PATH variable. In my case: D: GraphicsMagick coders This is also the place were GraphicsMagick expects to find the 'colors.mgk', 'delegates.mgk', 'magic.mgk', 'modules.mgk', and 'type.mgk' files.
One cool thing about the modules build of GraphicsMagick is that you can now leave out file formats and lighten you load. If all you ever need is GIF and JPEG, then simply drop all the other DLL's into the local trash can and get on with your life. WARNING: Always keep the 'xc' format, since GM uses it for internal purposes. You can elect to changes these things the good old 'hard-coded' way.
Two #defines are applicable. Defines.h has #define MagickConfigurePath 'c: GraphicsMagick ' To view any image in a Microsoft window, type gm convert image.ext win: Make sure Ghostscript is installed, otherwise, you will be unable to convert or view a Postscript document, and Postscript standard fonts will not be available. You may use any standard web browser (e.g. Internet Explorer) to browse the GraphicsMagick documentation. The Win2K executables will work under Windows '98 and later. The following are the instructions for how to build a Q:8 (or Q:16) DLL-based distribution installer package using Visual Studio 2008 Professional. This is the same procedure used to produce the release packages.
The PerlMagick steps are skipped as of GraphicsMagick 1.3.26):. Install prerequisite software:. Install Microsoft Visual Studio. Download and install Inno Setup 5. Download and install ActiveState ActivePerl (optional). Disable automatic indexing and virus scanning for the GraphicsMagick source tree. In particular, 'Windows Defender' in Windows 10 (and similar software in earlier Windows releases) has been observed to cause Visual Studio builds to fail since the virus scanner opens built libraries and executables to inspect whem while Visual Studio is still using them.
Indexing and scanning also cause significant slowdowns since there are many megabytes of files to index. Build GMVisualMagickconfigureconfigure.exe (if missing/outdated). Open workspace GMVisualMagickconfigureconfigure.dsp by double-clicking from Windows Explorer. Upgrade Visual Studio project (as required). Select Rebuild All to build configure.exe.
Close the project. Configure Initial GraphicsMagick Visual Studio Workspace. Use Windows Explorer to navigate to GMVisualMagickconfigure. Double-click on configure.exe to run configure program. Select desired build options: DLL build, Quantum Depth, 64-bit, OpenMP). Check Build demo and test programs.
Finish remaining configure wizard screens to complete. File - Close Workspace. Open Workspace, set build configuration, build GraphicsMagick software. Open workspace GMVisualMagickconfigureconfigure.sln by double-clicking from Windows Explorer. Build - 'Set Active Configuration' - 'All - Win32 Release' - OK. Optionally enable 64-bit (WIN64) compilation. ' Build / Configuration Manager.
/ Active Solution Platform / New / x64'. Open COREmagickmagickmagickconfig.h and edit any configuration settings you would like to change. For example, you might change QuantumDepth to 16 for a'Q:16' build. If using Visual Studio Professional Edition, and OpenMP support is desired, then select COREmagick in the Solution Explorer pane and use the right mouse button menu to select Properties. In Configuration Properties / C/C / Language set OpenMP support to 'yes'. Select 'Rebuild All'.
Click on '!' Icon to run configure program. Select DLL build. Check Build demo and test programs.
Click on Edit magickconfig.h and verify desired settings such as QuantumDepth. You can also defer this step to later by opening the header file COREmagick include magickconfig.h in the Visual Studio project.
Finish remaining configure wizard screens to complete. File - Close Workspace.
Build ImageMagickObject. Open Visual Studio Command Shell Window for WIN32 or WIN64. Registration key fsuipc rar file.
Change to GraphicsMagick project directory GM. cd GM contrib win32 ATL7 ImageMagickObject. BuildImageMagickObject clean. BuildImageMagickObject release. cd. Build PerlMagick extension (optional). Open Visual Studio Command Shell Window for WIN32 or WIN64.
Change to GraphicsMagick project directory GM. cd GM PerlMagick. nmake clean (only if this is a rebuild). C: Perl32 bin perl.exe Makefile.nt (or Perl64) Note that if multiple Perl's are installed, then it may be necessary to specify the full path to perl.exe in order to use the correct Perl.
nmake release NOTE: access to nmake requires that there be a path to it. Depending on how the install of Visual Studio was done, this may not be the case. Visual Studio provides a batch script in VC98Bin called VCVARS32.BAT that can be used to do this manually after you open up a command prompt.
Open GMVisualMagickinstallergm-win32-Q8-dll-full.iss (or gm-win32-Q16-dll-full.iss if QuantumDepth=16) by double-clicking from Windows Explorer. File - Compile. Test install by clicking on green triangle.
Test PerlMagick (optional). cd PerlMagick. nmake test (All tests must pass!). Test file format read and write. cd VisualMagick tests.
runrwfile.bat (All tests must pass!). runrwblob.bat (All tests must pass!). Run Magick test programs. cd Magick/tests. runtests.bat (All tests must pass!). Run Magick demo programs.
cd Magick/demo. rundemos.bat. Use gmdisplay to visually inspect all output files.
Distribution package is available named similar to GM VisualMagick bin GraphicsMagick-1.3-Q8-dll.exe Copyright © GraphicsMagick Group 2002 - 2017.
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.
Or read our to learn how to use this site. I have a Toshiba Satellite Pro 430CDS. Windows 98 would not boot in normal mode, but it would in safe mode.
In safe mode I could not access the cd drive, but when normal mode DID work the other day, I could. When trying to boot in normal mode, I got a message saying there was not enough extended memory to boot.
I booted in command prompt and formatted the entire hard drive, erasing windows 98. I have a windows 98 boot disc (ISO) which I burned to a CD-RW.
Obviously, the computer isnt recognizing the disc. I try to access drive D: by typing it, and it says invalid drive specification. Also, fdisk, as well as various other commands, arent recognized as commands any more. I may purhcase a swappable floppy drive to replace the CD rom drive, but I dont want to waste money if the drive is not the problem. All I want to do with this antique laptop is play old windows and DOS games.:/ What can I do now?
If this is an iso of the Windows 98 install disk, it cannot boot. You said it was a bootable iso. Was this custom made? If the computer has a floppy drive, you can create the, boot that which includes the CD rom drivers in order to recognize the drive.
You can also download a CD iso image of the startup disk. Don't select the one labeled noram.
Burn and boot the iso file. After it boots up, take out the CD and replace with the Windows 98 install disk. I can't remember what the drive letter is for the CD rom drive.
It may be D: Then at D: do a DIR command and you should see setup.exe. Type setup at the prompt. Windows should start the install. If this is an iso of the Windows 98 install disk, it cannot boot. You said it was a bootable iso. Was this custom made? If the computer has a floppy drive, you can create the, boot that which includes the CD rom drivers in order to recognize the drive.
You can also download a CD iso image of the startup disk. Don't select the one labeled noram.
Burn and boot the iso file. After it boots up, take out the CD and replace with the Windows 98 install disk. I can't remember what the drive letter is for the CD rom drive. It may be D: Then at D: do a DIR command and you should see setup.exe.
Type setup at the prompt. Windows should start the install. Thanks for the reply! Actually, the ISO that I burned to the disc was downloaded from the website you linked me. That's what I've been trying to boot. But it seems like the computer doesnt even recognize the CD drive.
It has no floppy drive, but I've just ordered an external floppy drive off amazon. I'm not sure if this will resolve the issue or not. Still, I would like to know how to make it find drive D. I'm not very good with CMD:/. Can the computer boot from a USB flash drive?
Older ones usually cannot. If it does, you can try booting the iso file using. Then if the CD is detected, you can install Windows 98.
Is a guide on installing Windows 98 from USB but it gets pretty involved. Edit: if the external floppy is a USB, then I don't know if it will work as the startup disk iso does not have USB drivers.
I played around with DOS drivers on a bootable disk for USB but that was a long time ago. Edited by JohnC21, 29 November 2014 - 02:14 PM. Can the computer boot from a USB flash drive? Older ones usually cannot. If it does, you can try booting the iso file using. Then if the CD is detected, you can install Windows 98.
Is a guide on installing Windows 98 from USB but it gets pretty involved. Edit: if the external floppy is a USB, then I don't know if it will work as the startup disk iso does not have USB drivers. I played around with DOS drivers on a bootable disk for USB but that was a long time ago. The computer has no USB port. But it does have a special external floppy drive port.
I had to order an external floppy drive made by toshiba especially for this type of computer. I pushed ESC while turning on to load the SYSTEM SETUP screen. Under Boot Priority, I only have the options FDD to HDD or HDD to FDD. No option for CD drive boot.
Is there anything else I can do? Okay, then that floppy should work. You can create a bootable floppy disk from the img file I linked to using but you need another computer with a floppy drive. I have a windows 7 computer with a USB floppy drive. Windows 7 should work, right? I mean, do I need another windows 98 computer to create the boot disk? If so, I'm out of luck.
How To Install Windows 95 Using Cd Commands![]()
Also, no command prompt commands are working. Sysedit, fdisk, etc.
They all return bad command or file name. DIR shows theres only 1 file on drive C:, COMMAND.COM Is this just because windows has been uninstalled? Will config.sys and the such be restored when windows 98 is reinstalled? Thank you very much for your help and time! No, if you have a USB floppy drive and Windows 7 it should work. RAWwrite shows it only works for up to XP but I beleive it works on Windows 7. If RAWwrite does does detect your USB floppy drive work, there is a way to do it in linux but it is a little more involved.
You would need to create a LIVECD of PartedMagic or Puppy. See if RAWwrite works first though.
Edit: When you reinstall Windows 98, it will create an Autoexec.bat and Config.sys file if I remember correctly, they both will be empty or have minimal commands. You will have to edit those with the required commands. Edit Edit: With only Command.com on C:, you will not have any commands like fdisk. Those will be on the startup floppy disk you will create.
Edited by JohnC21, 29 November 2014 - 03:20 PM. It's not too difficult to edit the autoexec.bat and config.sys files.
There are a lot of examples on the internet. Sometimes the games will even add there own setting to the files when installed if I remember correctly.
You may have a little issue with the settings for the Sound Card. Just for your info, I have played old DOS games on XP using an emulator called. It is a GUI front end for DOSbox, a vitrual dos environment. It has a bit of a learning curve but I was able to play an old DOS game called Starflight that was designed to be played using EGA graphics. I was able to get the sound effects for the game working too.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |