The DITA OT documentation has quite a bit of information about how to run the DITA OT in a Windows environment, but not much at all about running it in Mac OS. What is the procedure for running it in Mac OS (Mountain Lion)? Especially if you need to set environment variables (which is kind of tricky in Mac OS)
DITA-OT installation for OS X is documented in DITA-OT user guide.
Related
It's been my understanding the OS sits on top of the hardware. Is it more or less the same to run windows from a macbook? When installing SQL on a windows partition, does this install similar to an all Windows setup?
I've heard the kernel is the main connector between hardware and basic OS, so would the mac kernel cause potential differences in operation?
Would installing the linux OS also adhere to these rules?
Thanks, and sorry for the simple question.
Generally, you are correct to say that, installing different operating systems on the same hardware would be the same. You will be able to both install Windows and Linux on the same laptop (whether that would be an Asus brand laptop, or HP, or whatever). Once you install an OS on some hardware, and the OS is able to recognize the hardware, and is able to utilize it, then you are in the clear. What's important is to install on OS that is compatible with the architecture of the computer. So if you get a Linux distro that supports x86 architecture, then you would have to install it on hardware that is with a x86 architecture.
Side note: Modern OS's are very smart and they have a wide range of architecture support (list of Linux architecture support, Windows support for ARM, Apple also has a wide range of architecture support).
Since you are asking about a macbook and Windows, then the short answer is: there won't be a problem for you to install Windows on your mac. Apple even gives you Boot Camp to easily do this (there are also quite a bit of recent tutorials on this topic as well).
So the end experience would be almost the same as having Windows on any other machine.
I've heard the kernel is the main connector between hardware and basic OS, so would the mac kernel cause potential differences in operation?
This is true. The kernel is the heart of any OS, but once you have your Windows running, it would be using its own heart and it won't touch the mac kernel. So if you remove your macOS and install only Windows, then only the Windows kernel would be taking control of the Mac hardware. But if you load your macOS, then the Mac kernel would be running and operating on the hardware.
Will Windows run faster on Mac hardware than macOS on its hardware? It's debatable and I would assume not a lot of studies have been made in that sphere. But, at least, it will run.
But what about dual-booting your macbook with Linux? Technically, it is possible (and the principle is the same), but Apple have made restrictions to their firmware, limiting the option of having both a macOS and a Linux distro at the same time. What's so different here than the case with Windows? Well mainly that the firmware of the macbook (the software embedded in the hardware of the laptop) doesn't allow for Linux to be installed. Maybe things have changed, but these are the (not so recent anymore) news I know about (I guess there are still ways of installing Linux on mac hardware).
.nuget\packages\microsoft.quantum.development.kit\0.2.1809.701-preview\tools\qsc\qsc.dll'. Format of the executable (.exe) or library (.dll) is invalid.
How to repair qsc.dll?
Unfortunately, the quantum development kit only works with 64 bits OS (Windows, MacOS, Linux), and it appears that you are using a 32bit version of Windows.
I don't have any good option for you, except to upgrade the OS but I'm not certain there is a 64 bit version of Windows 10 Education.
As a limited option, you can try to execute some simple code in tio: https://tio.run/#qs-core.
I encourage you to create an item about this in https://quantum.uservoice.com/ where most of the feedback for the quantum development kit is gathered.
I've heard that Smalltalk is also an OS.
How can I install Smalltalk on my X86 instead of Linux or windows?
What are the steps to do that?
Any tutorials on installing Smalltalk on a bare-metal machine ?
I don't know if there is a standalone smalltalk environment, but you can try squeak, which runs above your os (linux, windows or mac). Not just an os but a complete working environment.
There was a project called SqueakNOS. That was the only post-PARC experiment to use Smalltalk directly loaded over the hardware, with no other operating system. It had even a version to work on an OLPC.
I don't know if currently someone follows that development, but it's very interesting and an excellent place to learn about hardware, in human-readable (but executable) terms. You can see and debug how a device driver works, for instance.
Smalltalk Virtual Machine is handling memory allocation, access to file systems, network connections, process (green thread)...
So viewed from Smalltalk world, it is very similar to an OS.
But how to implement the virtual machine without an underlying OS?
There is a project SqueakNOS and a fork PharoNOS meaning No Operating System, whose goal is to completely bypass the OS, and have Squeak/Pharo running on bare hardware.
So yes, it's possible.
But what you'll get with this is still a Smalltalk world, maybe not what you expect from a linux or windows distribution...
I need to test my C code for 32- and 64-bit versions of Windows (XP and 7) and Linux. But I have got access only to their 64-bit installations.
Question: Is it possible to use some boot-time settings or other hacks to run/emulate these OSes in 32-bit mode? If not, is there any other way to test the portability of my C code?
Note: The C code in question is not a full-fledged application but rather a .dll/.so file.
Neither Linux nor Windows 64Bit can run as 32Bit OS. Also, while you can run 32Bit executables on the 64Bit OS, it is not quite the same as running the same under a 32Bit OS. But it might work as a quick screening test. Besides, you certainly want that to work as well, right?
Your choices are full multi-boot setup, using VMs (might hide/expose bugs), being content with the emulation layer or running the other OS's on different hardware.
BTW: If you have Windows 64Bit, the license allows you to run 32Bit instead and vice versa. Anyway, you might want to check different language versions as well...
Mac OS X supports Microsoft OLE.
Does anyone know if it's possible to install the Win32::OLE perl module on mac OS X?
I know the module isn't supported on Mac, but would it be possible to try and compile anyway?
I don't think so that Mac Os X supports Microsoft OLE nativly. I think, it is some kind emulating or something like that.
Win32* modules checks the osversion ($^O if I am correct) to detect which os is run.
With force and without tests you could install this module but I think is won't work after install.
If you have an evidence that Mac OS X supports MS OLE please link that article into your question and you could ask the module maintainer to support OSX if it is really support OLE.
regards,
Modules in the Win32:: namespace, are for modules that work directly with Windows.
This means that it won't work on anything that doesn't present itself as Windows.
You could use a Win32 build of Perl running under WINE. Note that this would only be able to work with Windows versions of a program that are also running under WINE. (Assuming you can get it to work at all.)