Author Topic: A comprehensive guide to Odin available?  (Read 1828 times)

Doug Bissett

  • Hero Member
  • *****
  • Thank You
  • -Given: 1
  • -Receive: 46
  • Posts: 1251
    • View Profile
Re: A comprehensive guide to Odin available?
« Reply #15 on: August 25, 2019, 08:39:53 pm »
Quote
Looking at Microsoft's current direction, I expect to use their cloud products more in the future.

Personally, I avoid any contact with anything Microsoft, as much as possible. Their "cloud" is used for creating customized advertising, and, eventually, I expect that you will probably need to pay for using anything that is out there, including your own data.

Back in the 90's, IBM was pushing cloud technology (I think they called it something else). At that time, the internet was way too slow for it to be useful, and most people realized that it is NOT a good idea to let big companies know what you are doing with your computer. The only thing that has changed, is that people don't think about personal security anymore, until some company gets caught abusing their data (they all do it, most just don't get caught). Now, the internet is approaching being fast enough to be used, but the security risks are many times worse.

Tuure Linden

  • Jr. Member
  • **
  • Thank You
  • -Given: 4
  • -Receive: 2
  • Posts: 73
    • View Profile
Re: A comprehensive guide to Odin available?
« Reply #16 on: August 26, 2019, 11:04:00 am »
If you want to use cloud service, what would be the best alternative for Microsoft then? Google Drive shouldn't be it because they are worse than Microsoft when it comes to selling of your data. DropBox? Apple iCloud? At the moment DropBox seems to be only one that has a plugin available for OS/2 netdrive.

André Heldoorn

  • Hero Member
  • *****
  • Thank You
  • -Given: 119
  • -Receive: 19
  • Posts: 787
    • View Profile
Re: A comprehensive guide to Odin available?
« Reply #17 on: August 26, 2019, 12:08:07 pm »
Quote
Looking at Microsoft's current direction, I expect to use their cloud products more in the future.

Personally, I avoid any contact with anything Microsoft, as much as possible.

Their "cloud" is used for creating customized advertising, and, eventually, I expect that you will probably need to pay for using anything that is out there, including your own data.

In my book not using Microsoft's disks-scanning OS to use required Microsoft Office "solutions" qualifies as avoiding contact with Microsoft as much as reasonably possible. No more Windows, no more hours of monthly updates, less disk torture, and probably the same bleedin', unavoidable cloud in the future.

If only it was just your own data.

ivan

  • Hero Member
  • *****
  • Thank You
  • -Given: 2
  • -Receive: 35
  • Posts: 1026
    • View Profile
Re: A comprehensive guide to Odin available?
« Reply #18 on: August 26, 2019, 12:44:49 pm »
The IT industry are gearing up for the subscription model for all of Microsoft's cloud offerings.  There will not be any more 'buy once and use forever' Office offerings - if it is in the cloud you pay per month.

For those living and working in Europe there is also the GDPR which governs where data can be stored - if MS moves it out of Europe then the owner of the data can be held responsible if the data is leaked.

Last thing, who trusts a company that regularly uses its operating system to scan your computer and send data about what you are working on, your banking details and other sensitive information back to home office the be 'evaluated'?

Tuure Linden

  • Jr. Member
  • **
  • Thank You
  • -Given: 4
  • -Receive: 2
  • Posts: 73
    • View Profile
Re: A comprehensive guide to Odin available?
« Reply #19 on: August 27, 2019, 11:14:58 am »
And now I've tried it and confirmed that it's possible to install Windows 95 under the OS/2 version of DOSBox. So it's possible to run older 32 bit Windows software quite easily. Windows 98 might also work.

Tuure Linden

  • Jr. Member
  • **
  • Thank You
  • -Given: 4
  • -Receive: 2
  • Posts: 73
    • View Profile
Re: A comprehensive guide to Odin available?
« Reply #20 on: August 27, 2019, 11:50:05 am »
There are graphics glitches however. The OS/2 version of DOSBox is missing configuration files that Windows version has. So how can one set  [autoexec] and "cputype" settings?

André Heldoorn

  • Hero Member
  • *****
  • Thank You
  • -Given: 119
  • -Receive: 19
  • Posts: 787
    • View Profile
Re: A comprehensive guide to Odin available?
« Reply #21 on: August 27, 2019, 12:29:02 pm »
how can one set  [autoexec] and "cputype" settings?

For [autoexec] perhaps give the DosBoxGui (DOSBox front-end) a try, tab Config (scroll down there) and/or tab Autoexec.

Tuure Linden

  • Jr. Member
  • **
  • Thank You
  • -Given: 4
  • -Receive: 2
  • Posts: 73
    • View Profile
Re: A comprehensive guide to Odin available?
« Reply #22 on: August 30, 2019, 10:49:12 am »
Using the switch -conf configfilelocation and creating a configuration file makes it possible to change the settings. However whole DOSBox seems to crash if Windows 95 is running more than 20 seconds or so. Maybe some tweaks with the conf file is still needed. I'll look into it. I'm using Windows 95 OSR2 version. Maybe the original version would work better, who knows.

Joop

  • Sr. Member
  • ****
  • Thank You
  • -Given: 0
  • -Receive: 44
  • Posts: 487
    • View Profile
Re: A comprehensive guide to Odin available?
« Reply #23 on: August 30, 2019, 01:08:15 pm »
However whole DOSBox seems to crash if Windows 95 is running more than 20 seconds or so.
DOSBoxor Windows 95 wants the whole machine.You can't run these next to each other.

Andreas Schnellbacher

  • Sr. Member
  • ****
  • Thank You
  • -Given: 1
  • -Receive: 24
  • Posts: 440
    • View Profile
Re: A comprehensive guide to Odin available?
« Reply #24 on: August 30, 2019, 03:29:34 pm »
Using the switch -conf configfilelocation and creating a configuration file makes it possible to change the settings.
You can save adding this parameter by creating a file named dosbox.conf in the directory of the .exe.

For the upcoming next release of the OS/2 version, I've made additions to README.OS2. I append the relevant section here:


_____________________________________________________________________________

   Basic configuration
_____________________________________________________________________________

   For configuration, the file 'dosbox.conf' in the directory of 'dosbox.exe'
   (dosbox directory) can be used. For OS/2, an English version is copied
   from the 'eng' subdirectory to the dosbox directory, but only, if it
   doesn't already exist.

   __________________________________________________________________________
   Language

   To activate one of the optionally installed .lng or .lang files, ensure
   that dosbox.conf contains the following entry:

      [dosbox]
      language=<language_filename>

   <language_filename> should be replaced by e.g. 'deu.lng'. This file should
   either be placed in the directory of 'dosbox.exe' or the 'language' value
   must also include the subpath or full path of that .lng file. This entry
   must match and the file must exist. Otherwise DOSBox creates a trap on its
   start.

   Alternatively, you can also use the 'dosbox.exe' parameters:

     -lang <language_filename>
     -conf <config_filename>

   __________________________________________________________________________
   Keyboard

   In the OS/2 version, the keyboard layout is not selected automatically.
   The 'auto' value for 'keyboardlayout', which is the default, doesn't seem
   to work:

      [dos]
      keyboardlayout=auto

   It can be changed by changing the 'keyboardlayout' value. E.g. for using
   German keyboard layout with the default codepage 858 (similar to 850, but
   contains the Euro sign), add this to 'dosbox.conf':

      [dos]
      keyboardlayout=gr

   Alternatively, it can be changed with the 'keyb' command:

      [autoexec]
      keyb gr

   Some usual keyboard layout values for existing translations:

      us       eng  English
      gr       deu  German
      fr       fra  French
      it       ita  Italian
      no       nor  Norwegian
      ru       rus  Russian
      cz       cze  Czech
      dk       dan  Danish
      es       esp  Spanish
      fi       fin  Finnish
      hu       hun  Hungarian
               kor  Korean (DBCS)
      nl       ned  Dutch
      pl       pol  Polish
      po       prt  Portuguese
      tr       tur  Turkish

   See the table in 'KEYB\layouts.txt', column 'File' for more keyboard
   layouts and section '8. Keyboard Layout' in 'README'.

   Also bundled is mKEYB, a replacement of KEYB, which has the keyboard
   tables compiled in. See the help file in 'mkeyb\README.TXT'.

   __________________________________________________________________________
   Configuration file with NLS comments

   A recent and complete config file with NLS comments can be created as a
   starting point:

      o  Add the language file and the keyboard layout values to
         'dosbox.conf', as described above.

      o  Start 'dosbox.exe' with an existing 'dosbox.conf'.

      o  From the host system, rename 'dosbox.conf' to 'dosbox.conf.bak'.

      o  Export the current configuration, together with NLS comments to the
         dosbox directory:

            config -wcp dosbox.conf

         This new file contains the values of the renamed file 'dosbox.conf'
         from the startup of DOSBox and NLS comments, if the 'language'
         value was configured before.

   You can also use one of the examples in the NLS subdirectories as
   template.

   __________________________________________________________________________
   Mount host directories as local drives

   For mounting host directories, use the mount command:

      [autoexec]
      mount <local_drive_letter> <host_dir>

   Example:

      mount D F:\Apps\DOSBox

   __________________________________________________________________________
   Further information

   See the detailed descriptions in 'README', sections '4. Internal Programs'
   and '3. Command Line Parameters'.


Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 11
  • -Receive: 149
  • Posts: 2169
    • View Profile
Re: A comprehensive guide to Odin available?
« Reply #25 on: August 30, 2019, 04:20:29 pm »
Microsoft broke Win32's (and Win32) on OS/2 by forcing some of the system DLL's to load in the high memory arena, which didn't exist on OS/2 at the time. That was why Win32s 1.30 didn't work unless a couple of DLL's from 1.25 were used. Whether DosBox on OS/2 allows full access to high memory I have no idea but wouldn't be surprised if the answer is no.
If the answer is yes, likely VIRTUALADDRESSLIMIT needs setting to a large number such as 3072.
« Last Edit: August 30, 2019, 04:40:15 pm by Dave Yeo »

Jochen Schäfer

  • Jr. Member
  • **
  • Thank You
  • -Given: 18
  • -Receive: 7
  • Posts: 99
    • View Profile
Re: A comprehensive guide to Odin available?
« Reply #26 on: August 31, 2019, 11:52:32 am »
Let's say it like this: I didn't do anything to ensure access to high memory. IIRC, all memory allocation goes through LIBC(++) and SDL. So it really depends on them.

Tuure Linden

  • Jr. Member
  • **
  • Thank You
  • -Given: 4
  • -Receive: 2
  • Posts: 73
    • View Profile
Re: A comprehensive guide to Odin available?
« Reply #27 on: September 01, 2019, 01:23:12 pm »
Some programs require Win32S ver 1.3. So they really work ok if you copy the certaind DLLs from the 1.25 version? If they do, which DLLs have to be copied?

Dave Yeo

  • Hero Member
  • *****
  • Thank You
  • -Given: 11
  • -Receive: 149
  • Posts: 2169
    • View Profile
Re: A comprehensive guide to Odin available?
« Reply #28 on: September 01, 2019, 06:19:04 pm »
http://www.os2voice.org/VNL/past_issues/VNL0503H/vnewsf3.htm has directions for creating a hybrid. Basically uses
Code: [Select]
shell32.dll
comctl32.dll
oleaut32.dll
ole2thk.dll
ole32.dll
from 1.30, over 1.25 if I'm reading it right.