Sie sind nicht angemeldet.

Lieber Besucher, herzlich willkommen bei: GEOS-InfoBase-Forum. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.

21

Montag, 29. August 2016, 13:22

Hi,

auch das DOS-SDK funktioniert damit wieder. Ich kompilieren und gleichzeitig ausprobieren. Interessant wäre evtl. auch mal zu sehen, ob ich das SWAT des SDK zum Laufen bringe. Mehrere DOSEMU-Instanzen, die sich über eine gemeinsame serielle Schnittstelle unterhalten ... ist ein Versuch Wert.

Hat eigentlich schon jemand das NT-SDK unter Linux zum Laufen gebracht?

Viele Grüße

Uli

>>> Je weniger WINDOWS um so besser. <<<
Hallo Uli

Das NT-SDK könnte wahrscheinlich schwierig werden. Meines Wissens hatte ein Benutzer aus dem BBX-Forum die DOSBOX gepatcht und damit das NT-SDK verwenden können. Dies könnte rein theoretisch auch unter DOSEMU2 gemacht werden. Details habe ich aber nicht mehr im Kopf.

Wenn SWAT mit dem DOS-SDK auch funktioniert, wäre das auch ein schöner Fortschritt. Muss dann wohl auf die langen Dateinamen von Quelldateien verzichten. Gibt es noch andere Einschränkungen des DOS-SDK ?

Gruss
Andreas

22

Montag, 29. August 2016, 17:58

Dos-Sdk

Hallo Andreas,

ich besitze das DOS-SDK für den HP OmniGo. Wenn ich den Rainer richtig verstanden habe, besitzt das SDK 2.x wohl noch den ein oder anderen Fehler im Document-Handling, weshalb er wohl lieber eine NT-SDK-Variante benutzt. So tief stecke ich in der SDK-Thematik aber nicht drin, dass ich das irgendwie bewerten könnte.

Viele Grüße
Ulrich Cordes

>>> Je weniger WINDOWS um so besser. <<< :D

23

Montag, 29. August 2016, 18:50

Das NT-SDK kennt beide Verzeichnistrenner: / und \
Das NT-SDK kennt lange Dateinamen (und nutzt sie auch für die temporären Dateien beim Kompilieren).
Das NT-SDK kennt beide Arten, Kommentare zu markieren: // und /* */
Für das NT-SDK wurden einige Fehler behoben, z.B. das Jahr-2000-Problem in Grev.
Das NT-SDK sollte theoretisch "am fehlerfreisten" sein, allerdings gibt's tatsächlich neue Fehler, z.B. in sound.h. Fehler aus dem Omnigo-SDK (in "INITFILE.H", "FILE.H" und im GLUE) wurden jedoch definitiv behoben.
Beim NT-SDK funktioniert SWAT auch lokal.
There are two rules in life:
1. Never give out all of the information.

hanslse

Fortgeschrittener

Beiträge: 275

Beruf: Systemadministrator

  • Nachricht senden

24

Dienstag, 30. August 2016, 11:54

DOSEmu2 seems very cool, Thanks, Bolle for your good work! I have a couple of questions, which anyone can jump in and answer. I tried DOSEmu before and I had some problems that I could not get by, one was that I had to manually tweak Linux every boot, which made the whole operation quite useless, and I failed to automate the whole boot process. I can't recall what it was, hopefully this will not occur for me now. I plan to use my Eee PC 701 with 4 GB of SSD and 32-bit CPU, and run Geos from a flash memory (SD card). I want to set up the Linux and the DOSEmu part on the tiny SSD. So there is no room for an ordinary Ubuntu distribution.

Any hints of a small textbased linux that will work with DOSEmu2?

Is it possible to call (start) for example a linux browser and email software from Geos in DOSEmu2?

BR,
Hans

25

Dienstag, 30. August 2016, 12:30

Hello Hans

The only setting I could imagine is the mmap minimum address: "vm.mmap_min_addr = 0". That allows the access to the first 64kB of RAM to other programs then the Linux kernel. This setting is only needed on 32-bit systems, on 64-bit system, the vm86 calls are completely emulated. DOSEmu2 in VM86 mode would run without it too, but slow(er).

On Ubuntu / Debian based systems, the "vm.mmap_min_addr" can be set in the file "/etc/sysctl.d/10-zeropage.conf". Use the file "/etc/sysctl.conf" on other distributions, if they don't have a special config file for it.

Using DOSEmu2 on 32-bit systems, I would advice to go the KVM route ($_cpu_vm = "kvm") instead of VM86. Maybe, the "vm.mmap_min_addr" can be applied there too, but I haven't tested it. Wine and QMEU uses this setting too, but in case of pure KVM, I don't know.

Andreas

26

Mittwoch, 31. August 2016, 20:44

I plan to use my Eee PC 701 with 4 GB of SSD and 32-bit CPU, and run Geos from a flash memory (SD card). I want to set up the Linux and the DOSEmu part on the tiny SSD. So there is no room for an ordinary Ubuntu distribution.
I use another configuration on the EEE 701: Linux Mint Debian2-Edition on a 16 GB SD-Card and Dosemu (1) and Geos are on the 4 GB SSD.

hanslse

Fortgeschrittener

Beiträge: 275

Beruf: Systemadministrator

  • Nachricht senden

27

Dienstag, 6. September 2016, 15:15

I have installed EasyPeasy on my EeePC 4G (701) and planned to use Geos on a 2 GB SD card. However, I have problems download all the tools, it seems that EasyPeasy is not compatible with DOSEmu 2. Some libraries doesn't work and some I can not download because I run out of space.
I have scaled down EasyPeasy a bit and I can probably scale it down more. I guess I will need a DOSEmu2 binary, to be able to install on these meager hardware. I will try DOSEmu 1.4 once again. If that doesn't work, I will try geobart's solution.

Hans

28

Dienstag, 6. September 2016, 22:41

Have you tried our little installer? With EasyPeasy the script should work.

http://geodb.org/src/geosemu_install.zip

(install.txt)

Wolfgang

hanslse

Fortgeschrittener

Beiträge: 275

Beruf: Systemadministrator

  • Nachricht senden

29

Mittwoch, 7. September 2016, 16:56

Hi!

Thanks geobart, I have now managed to install the package, but I don't have the glibc 2.15 installed. I think I have now managed to download the right glibc 2.15 package as a cpio package, but I can't figure out how extract it to the system. I have tried to extract it, but it will only unpack to the Download folder, I can't move it to the system. Seems that Easy Peasy is very restricted. Maybe I can extract it to the system as a super user from the Terminal, but I have not figured out how to do it yet.

Hans

30

Mittwoch, 7. September 2016, 18:43

sudo nemo, nautilus or whatever your file manager is called.

31

Mittwoch, 7. September 2016, 22:28

Why the glibc 2.15 ?

hanslse

Fortgeschrittener

Beiträge: 275

Beruf: Systemadministrator

  • Nachricht senden

32

Donnerstag, 8. September 2016, 13:42

Why the glibc 2.15 ?

Because I get an error message ?( when I start GeosEmu: `GLIBC_2.15' not found (required by /usr/bin/dosemu.bin)

Hans

hanslse

Fortgeschrittener

Beiträge: 275

Beruf: Systemadministrator

  • Nachricht senden

33

Donnerstag, 8. September 2016, 13:52

sudo nemo, nautilus or whatever your file manager is called.

Thanks! Well, sometimes the most obvious is far away. It is nautilus in Easy Peasy.

Hans

hanslse

Fortgeschrittener

Beiträge: 275

Beruf: Systemadministrator

  • Nachricht senden

34

Donnerstag, 8. September 2016, 14:34

Sorry, a message I can't interpret, is there anyone here who knows the solution?

"the -n option to bypass the the system configuration files is not allowed with sudo/suid-root"

Hans

hanslse

Fortgeschrittener

Beiträge: 275

Beruf: Systemadministrator

  • Nachricht senden

35

Donnerstag, 8. September 2016, 14:47

Sorry, a message I can't interpret, is there anyone here who knows the solution?

"the -n option to bypass the the system configuration files is not allowed with sudo/suid-root"

Hans

Forget, I have solved it! I tried to run the bash script with sudo. It works better with just bash as an ordinary user. However, I get more errors, missing sound drivers and so on, and the DOSEmu flashing by and so on, I guess I need to check the bash script.

Thanks,
Hans

hanslse

Fortgeschrittener

Beiträge: 275

Beruf: Systemadministrator

  • Nachricht senden

36

Donnerstag, 8. September 2016, 16:50

New error :(

ALSA lib rawmidi_hw.c:233: (snd_rawmidi_hw_open) open /dev/snd/midiC0D0 failed: No such file or directory. I get a crash and then bounce back to the prompt.

I have checked the contents of the /dev/snd folder and I have no midiC0D0 file, but I have a midiC1D0, midiC1D1, midiC1D2, midiC1D3.
What can I do? IS there something to edit somewhere?

Secondly, when I check for the DOSEmu.conf, I find three DOSEmu.conf. One of them is in the installation folder, but the other two is in the linux system, which is the editable one?

BR,
Hans

37

Donnerstag, 8. September 2016, 18:49

Forget, I have solved it! I tried to run the bash script with sudo. It works better with just bash as an ordinary user.
Hello Hans,

sudo is useful for the installation - you mentioned you weren't able to move the downloaded files into the recommended directories. Otherwise some programs have a "checkuser"-function to avoid to execute them as root.

Wolfgang and Andreas may be able to tell you which alsa-packages (sound) you also have to install.

Martin

hanslse

Fortgeschrittener

Beiträge: 275

Beruf: Systemadministrator

  • Nachricht senden

38

Freitag, 9. September 2016, 12:58

Well, by using sudo Nautilus, I was able to move files, so my lack of the GLIBC 2.15 is solved, I extracted and copied the files to the appropriate folders, and it have gone well, the GLIBC is installed now. What fails me now is the ALSA driver. I know that I have solved this previously, but I can't recall how I did it :(

BR,
Hans

39

Freitag, 9. September 2016, 17:33

New error :(

ALSA lib rawmidi_hw.c:233: (snd_rawmidi_hw_open) open /dev/snd/midiC0D0 failed: No such file or directory. I get a crash and then bounce back to the prompt.

I have checked the contents of the /dev/snd folder and I have no midiC0D0 file, but I have a midiC1D0, midiC1D1, midiC1D2, midiC1D3.
What can I do? IS there something to edit somewhere?

Secondly, when I check for the DOSEmu.conf, I find three DOSEmu.conf. One of them is in the installation folder, but the other two is in the linux system, which is the editable one?

BR,
Hans

Hello Hans

I get the same message, as I don't have a kernel module loaded which create the MIDI device files. For PC/GEOS, this message shouldn't hurt.

So, your crash has likely nothing to do with this message. Do you have a "~/.dosemu/boot.log" ?

Greetings
Andreas

hanslse

Fortgeschrittener

Beiträge: 275

Beruf: Systemadministrator

  • Nachricht senden

40

Samstag, 10. September 2016, 12:02

Hello Bolle and everybody!

First, I have solved the problems, I presumed some things, which was impossible to do. The "crash" was Exitemu command combined with the ALSA error message. My incompetence? Well, I figured it all out ;)

I have managed to start Ensemble, and now I need to start all the work to tweak it.

The error message from the ALSA driver is a bug or a misconfiguration of LInux/Ubuntu. I got a lot of hits in Google when I managed to set the search the right way. I get the message as there is no real Midi in my netbook. Bolle, I also found our Yahoo mail discussion from 2011, and I got the same ALSA error message back then. So, sorry for my short memory ;) I will use the mail discussion as my reference.

What I recall the DOSEmu installation is set to work in a Linux window?

Will there be any similar installer for DOSEmu2, with a compiled library? That will be good for me:)

Thanks, Wolfgang, Martin and Bolle for your support!

Hans

Ähnliche Themen

Thema bewerten