What 039;s A .dmg File: Learn How to Create and Mount Disk Images on Mac

ODBC Manager is a GUI tool for configuring drivers and creating/managing DSNs. The tool is optional because you can also create DSNs manually by editing the appropriate odbc.ini file. ODBC Manager is available from:

If you are creating the first user or system DSN for the ODBC driver, ODBC Manager creates the odbc.ini file in the corresponding directory for the type of DSN you are creating. If you are creating additional DSNs, ODBC Manageradds entries for each DSN to the existing odbc.ini file.

What 039;s A .dmg File

DOWNLOAD

If a user or system DSN has already been created for the driver, add the new entry to the odbc.ini file that already exists in the corresponding directory for the type of DSN you are creating. If you are creating the first DSNfor the driver, you must manually create the odbc.ini file and add the entry to the file.

pwd is not the mounted .dmg image. I don't know how to enter into the mounted image drive to see its contents. So in case what I said sounds like I see the files in the mounted image no this is not the case. I do not know how to access or even change the pwd within Terminal. I was hoping to see the mounted drive through Finder but I do not see that.

I used the command from Terminal to convert but was not successful. Instead, I used Disk Utility, attached the Volume (yes I got the same message again, "no mountable system files") however, Disk Utility nevertheless attached the image, which I was able to do before anyways.

I created a new image. This time this image was writable however, it still would not mount using -noverify -nomount. However, this time I was able to scan it with Disk Drill with exact file locations and folder hierarchy as I had. Recovering all from thereon was a breeze.

The platform-dependent installation programs use the inbuilt SapMachine during the installation, thus no installed Java Virtual Machine is required. Depending on your platform, the following files are applicable:

Depending on the location of the configuration file, you can enter either a full pathname (for a local file) or an URL (for a file located on an intranet web server).

So what the Include-logic means is that for items of the Included file, you cannot edit or delete any such items. On the other hand, you can still create new items or create a duplicate of existing items, and any such new or duplicated items are then editable and deletable.

So typically you would have the remote server file being specified in Preferences, and then any new or copied-then-modified items that you create, are being saved locally in SAPGUILandscape.xml (though most users will not need or want to make new entries).

Now, if you have specified either via The Server Option or The Local Option a list of SAP systems in the xml file, and you open SAPGUI, it can happen that only some empty workspace appears; if this happens, then go to View -> Show All Workspaces, and then the full list of SAP systems should be visible under the relevant workspace(s).

(c) Reinstall the SAPGUI client (e.g. as shown above in this blog; if using the JAR method then make sure you have suitable java and javac versions available and environment variables set); then get any needed local xml files back into the (regenerated via install) folder: /Library/Preferences/SAP/

For whatever reason the dmg installer option didn't work for me ("Installer.app is damaged and can't be opened. You should eject the disk image"), but as the P-user media also includes a JAR, so it was easy enough to smoke-test installing this version 7.70 rev 1 successfully.

I don't work for SAP so I can only tell you what I have observed, which is that the organisation I work for has licensed SAP SSO, and that I downloaded the client (as shown in the blog) from SAP Software Downloads using that organisation's S-user that is assigned to me.

a) The SAP Secure Login Client is not available for me as my organisation did not buy it. From what I read in some SAP notes it should be free of license costs if you use only encrypted communication from SAPGui to the SAP backend, but anyway it is not available for download

For issue (a) it is difficult for me to confirm that the SLC is not available for download for non-SAP-SSO subscribers, as the organisation I work for has subscribed to the SSO product, so as we see in the blog I can easily download the SLC. (As a law-abiding citizen I am not going to distribute SAP's property onwards, so people need to work out themselves what are the allowed ways to get this software).

Maybe worth to mention, for SLC you can define settings like CAPI filters and SNC modes in /Library/Preferences/com.sap.SecureLoginClient/settings.plist. This is helpful to hide invalid certificates or certificate with non-matching key usage types from the profiles list.

For me it was necessary to also edit my /Library/Preferences/SAP/settings file and remove the lines starting with @SAPUILANDSCAPE and @LandscapeLastCentralLS before I could reset with a fresh /Library/Preferences/SAP/SAPGUILandscape.xml.

Initial attempts to use use SNC with SAP GUI for Linux fails - error: cannot find file sncgss.so. I downloaded the SAPCRYPTO Library and will use the file libsapcrypto.so by setting the environment variable SNC_LIB to point to it in my users .profile file - I put all content of SAR in my /sec directory. (A possible alternative might be to create a soft-link called sncgss.so pointing to libsapcrypto.so - have not tried). You will also need to use the sapgenpse utility.

Create a PSE in your /sec directory (or, alternatively you can use different directory but you would need to also set the SECUDIR environment variable). Seems like you need to use the name SAPSNCS.pse for the PSE file (I tried different name and that did not appear to work):

The XQuartz file is provided as .dmg file. A .dmg file is kind of like an USB stick in a file and can be handled more or less the same way. To install from a .dmg file you usually do the following :

------juan [ Reply to This # ] Convert .dmg files to .iso files for buring elsewhere Authored by: commandus on Aug 11, '05 11:23:42AM Here's an alternative script using the bash shell:----------------------------------------------------------------#!/bin/bashecho "Converting "$1".dmg to "$1".iso:"hdiutil convert "$1".dmg -format UDTO -o "$1".isomv "$1".iso.cdr "$1".iso----------------------------------------------------------------Save as dmg2iso (Or whatever) and run:chmod +x dmg2isoTo use:$ dmg2iso imageYou don't have to include the ".dmg" bit. It's assumed. The output file will be: image.isoEnjoy. Commandus

the whole idea for me is so i can burn ISO files on a windows or linux box. my mac doesent have a CDR drive, and the chance of me getting one soon is slim. so to be able to make ISO files out of DMG files and then burn elsewhere is handy.---Lotas Smartmanwww.lotas-smartman.netwww.the-hairy-one.comwww.lsn-blog.tk

the ISO image standard does not allow internal compression. You'll have to gzip or stuff or zip (or whatever) the resulting file, if you want to send it or whatever.This is partly why I'm a big fan of compressed DMG's... no muss no fuss. but also no interoperability with lesser OS'es ;)---In /dev/null, no one can hear you scream

Found this on another website... I dont own a Mac so .."...the hdiutil is a command that is native to MAC, not Windows... "Also I found this and tested it ...to convert an Image (.DMG, .ISO...or whatever) use UltraISOAwsome Tool!....Easy as pie baby! (point and click!)They have a trial download (Good for up to 3GB of data) p.s. If you want to see the files on Windows like you do when you open a folder then you will have to "extract" the files from its .ISO, .DMG format or whatever format it is in. Althought, UltraISO will show you the files before it converts them or extractes them in its window.Good Luck!Remote Operative

Here's an alternative script using the bash shell:----------------------------------------------------------------#!/bin/bashecho "Converting "$1".dmg to "$1".iso:"hdiutil convert "$1".dmg -format UDTO -o "$1".isomv "$1".iso.cdr "$1".iso----------------------------------------------------------------Save as dmg2iso (Or whatever) and run:chmod +x dmg2isoTo use:$ dmg2iso imageYou don't have to include the ".dmg" bit. It's assumed. The output file will be: image.isoEnjoy. Commandus

Alternative method:Open Disk Utility, convert the DMG file to a CD/DVD Master (it'll have the extention .cdr), change the extention to .iso, transfer it over to your PC and burn it with whatever software you have.Originally posted on macrumors by: vniow

I am confused what to write in the comand. I am confused what to write for first Path and then another Path in the end.I have file name: iLife , on C Drive (its directly on C, not in any folder). and I want to save that file on Desktop.Can anyone help me... Please... You can contact me on: jaypatel06@yahoo.com Thanks

Rip a CD-ROM to a .iso file:In disk utility, get info on your mounted CD to see what device name it is. On mine it's /dev/disk1s0.hdiutil create -srcdevice /dev/disk1s0 -format UDTO filename.isomv filename.iso.cdr filename.iso

I think there is some confusion between naming something ".iso" (which, if a .cdr image, is then burnable in Windows) and the actual ISO-9660 *filesystem*, with or without the Joliet extensions, which is an actual burnable, mountable and useable VOLUME in Windows. If you do this: hdiutil convert /path/to/filename.dmg -format UDTO -o /path/to/savefile.isoor more properly this: hdiutil convert -format UDTO -o /path/to/outfile /path/to/source.dmgYou end up with the same thing: A .cdr disc image. Leave the ".iso" off to see. So why not just make a .cdr ("CD/DVD Master") from Disk Utility in the first place (or select a .dmg and pick Convert in Disk Utility) and rename the .cdr to .iso? It's the exact same thing. But the resulting burned CD has only 1 filesystem - HFS+ (Mac OS Extended) that is not very useful in other OSes.But for Windows compatibility (a CD or volume you can actually mount) you want the ISO-9660 *filesystem*, with or without the "Joliet extensions" to the ISO specification. Or maybe you want UDF for DVDs. But what if you could have HFS+, ISO-9660, Joliet, *and* UDF all on the same image - and have it be smaller than the file created by the above Terminal commands? Well, you easily can - here's the quick and dirty how-to:1. Drag the .dmg file (the CD, DVD or volume of which you want to use in Windows or Linux) to your Desktop.2. Then go to the Terminal and type: hdiutil makehybrid -o /Desktop/ /Desktop/3) Press Enter.That's it! The "example.dmg" which you dragged to your Desktop is , and is just any name for the resulting image file. You can rename later, so don't dork it up - leave out spaces, symbols, etc. DO NOT add .iso, .dmg, .cdr, etc. to the end of . The correct filename extension will be added only if it isn't part of the provided name. Also, the path is case-sensitive. The currently logged-in user likely does NOT have a /desktop, but DOES have a /Desktop directory.But wait - it gets better! can be the name of a FOLDER! It does not have to be a .dmg image file. Just get the path correct (does not have to be /Desktop if you want to make an image from a folder elsewhere, or a disc image elsewhere) and "viola" - you get a perfect hybrid disc image file useable in virtually *every* modern OS. And can even be a hard-drive! Heck, for all I know can be a very large database file by itself... try it. I'd be interested to know.To see the 411 on this, type "man hdiutil" in the Terminal. Hit Space or Return until you get down to the VERBS section. Look at "convert", then look at "makehybrid". The "convert" verb is basically all the Disk Utility functionality, but in the Terminal. Boo. But look at the "makehybrid" verb; after the 4 filesystems (-hfs, -iso, -joliet, -udf) under "makehybrid" is this:"By default, if no filesystem is specified, the image will be created with all four filesystems as a hybrid image. The data area of the image is shared between all filesystems, and only directory information and volume meta-data are unique to each filesystem. This means that creating a cross-platform ISO9660/HFS+ hybrid has a minimal overhead when compared to a single filesystem image." Hizzaa!DMG Converter ( ) can create ISO filesystems, but it cannot CONVERT images to ISO filesystems, only make new images using it. So if you mount the image first and then use DMG Converter on the mounted volume, "converting" the disc image is the same as "making" a new image from the mounted volume. But God help me I'm not that bright, so the menu options are sort of confusing to me... This is 1 instance where using the Terminal is actually easier!I tried this "hdiutil makehybrid" command on a 458 MB .dmg file and got a hybrid .iso that was 530 MB in size. Using "hdiutil convert" gave me a 592 MB ".iso" file that was actually a .cdr - and only had the single HFS+ filesystem - so it did not work in Windows. I'm much happier w/ the true ISO that is 60 MB smaller and has 4 filesystems! There is no compressed image format for Windows, so if you want a smaller file just zip or stuff your final hybrid image. 2ff7e9595c