ok,

configure --with-amigaos ; no errors
make

vvfat.cc: In function `Bit16u fat_datetime(long int, int)':
vvfat.cc:502: implicit declaration of function `int localtime_r(...)'
make[1]: *** [vvfat.o] Error 1
make[1]: Leaving directory `/Temp/bochs-2.6.1/iodev/hdimage'
make: *** [iodev/hdimage/libhdimage.a] Error 2

Help me with this one.
Just download the SDK and then the latest source for 2.6.1 if you want to help.


[ Edited by bash64 15.05.2013 - 19:26 ]

Well... is it that hard to google? localtime_r() can be implemented by using localtime() for your purposes.

Update:

I have veered off into making bochs 2.6 just work for now.
There is a serious bug in that .iso files lock up a lot.
Also, there is a 2gb hard file size limit!
OMG!

I got xp pro with no service packs to install to a 2gb hard file using qemu manager 7.0 on windows 7 64 bit.

This hardfile resets repeatedly on mos.

I am attempting to repair windows but cannot due to the .iso lock up issue.

Currently, I just figured out how to force bochs to use my physical cdrom drive in the config file.....buuuut something is wrong with the powerbook driver.
The cdrom is idemacio.device 0, the cdrom cannot be detected using this device.
in the config file it would be :

ata0-slave: type=cdrom, path="idemacio.device 0", status=inserted, biosdetect=auto, model="Generic 1234"

There was even an example of using ide.device 2.

Nope. Won't boot. Cannot get around it for now.
I will be looking to buy a usb cdrom drive and using usbscsi.device instead.

According to bochs networking is well supported.
However, you have to compile the plugins which the various people who have worked on the MOS version (and their has been a few) did not bother to do.

What is even sadder is that they left us no source code.
This is open source and they didn't bother to pass on the source code.
%#$%#@$



I need the code to the MOS version of bochs 2.6 to begin with. This will save a lot of time.
Please help me hunt this down.
Thanks

ok,

You won't believe it but the solution to the .iso file locking up is very simple.
Copy your .iso file into ram:

Windows xp pro is now repairing itself from cd....

It apparently takes way to long for bochs to read the iso and a timeout occurs and then it locks up.




[ Edited by bash64 09.05.2013 - 23:14 ]

So lets recap how to install xp in MOS:

Download bochs-2.6.lha
Dearchive and rename main folder to 'bochs' instead of boch-2.6 (not really needed if you keep the hardfile in the bochs/ folder instead of the images subfolder).

The default .bochsrc config file needs a few changes but not much.

Run bximage and answer the questions with the defaults.
Make the hardfile image 'flat' and 2048mb in size (no bigger!).
bximage will give you the line to add to .bochsrc. Do so.
Make sure no other ata0-master lines are uncommented.

Example for 2048mb hardfile:
ata0-master: type=disk, path="c.img", mode=flat, cylinders=4161, heads=16, spt=63

Add a line for the cdrom as such:
ata0-slave: type=cdrom, path="ram:xp.iso", status=inserted, biosdetect=auto, model="Generic 1234"

Rip xp pro with NO service packs to an ISO image and name xp.iso and copy to ram:

Modify the boot option:
boot: cdrom,disk

Modify ram to 128mb for guest. There is a reason, see final comments.

Open shell and enter bochs folder:
>cd bochs

Run bochs:
>bochs

Pressing enter at the menu will default to option 6 which will run bochs with the default config file.

You should see windows xp cd asking you to hit a key if the hardfile has windows on it, or it will just autorun the windows setup.

A whole lot of editing of the .bochsrc file doesn't seem to be needed. Its MOS ready.

And that is what has worked for me so far...

P.S. xp pro with any service packs is too big to install to 2gb.
Also, keep your ram, while installing, down to 128mb.
if you go bigger like 512mb xp will create a huge hiberfil.sys file to match and eat up 512mb of hard drive space. Left me with only 56mb free after installing when I did that.
You can turn off hibernation in control-panel->power-options and the hiber file will be deleted automatically.


[ Edited by bash64 09.05.2013 - 23:39 ]

http://i933.photobucket.com/albums/ad171/bash64000/4_zps30b0cf36.jpeg

ok, its repairing.....if it fails I will just reformat and go for a new install..

If this goes well, then what we really need is to get one of the network card plugins compiled, no need to recompile 2.6.

Anyone interested in working on that?
There are a few virtual network devices available also.
What ever is easiest.

> According to bochs networking is well supported. However, you have to compile
> the plugins which the various people who have worked on the MOS version
> (and their has been a few) did not bother to do.

I reckon it could have something to do with this:

https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=9177&forum=9&start=48

The porter of Bochs 2.6 has this to say on the topic (translation by me):

"Network doesn't work because the promisc mode doesn't work and the sendings disappear into nirvana instead of going into the LAN. It does work if I send packets with correct MAC and IP. It seems MorphOS internally prevents the sending and receiving of raw external packets (because it could as well be fake packets). For this I have to think out a solution, maybe a mini tunnel or similar."

> What is even sadder is that they left us no source code. This is open source and they
> didn't bother to pass on the source code. [...] I need the code to the MOS version of
> bochs 2.6 to begin with. This will save a lot of time. Please help me hunt this down.

Please answer my question I asked you there:

https://morph.zone/modules/newbb_plus/viewtopic.php?topic_id=9177&forum=9&start=46

I used the email in the archive.
j.vancalrehden or something like that.
I also found several other emails using google and tried them.
I always get a returned email.
No such address.

I did not get the impression that the plugins were ndis drivers and needed a w32 wrapper.
I thought they were complete emulation.

>>> I sent an email to the developer of bochs for MOS and the email is a dead end.
>>> See if you can get a hold of the guy. We'd like a copy fo the MOS source code.

>> Who did you try to email and at which email address?

> I used the email in the archive. j.vancalrehden or something like that.

Which archive would that be specifically? And what makes you believe this "j.vancalrehden" guy is the "developer of bochs for MOS"?

Do I really need to tell you to download the archive and look in the README like I did?

>> Which archive would that be specifically?

> download the archive

Again: which one?

> look in the README like I did

I'll do as soon as you tell me which archive that README with the "j.vancalrehden or something" email address is included in.

http://morphos-files.net/download/Bochs

>>>> Which archive would that be specifically?

>>> download the archive

>> Again: which one?

> http://morphos-files.net/download/Bochs

Thanks. The only MorphOS-specific README file I can find in that archive is readme.MorphOS (1597 bytes). This file doesn't contain any email address, so I'm confused about the "j.vancalrehden or something" email address you say would be mentioned therein. Is it really this README file you mean? If not so, which README file is it that contains said email address of the alleged "developer of bochs for MOS"?

Btw, now that I know which MorphOS port of Bochs you're in search for the source code of, I think I can help you. Have a look there:

http://www.morphos-files.net/find.php?find=bochs

It clearly says "Ported by Thore Sittly". So obviously, this would be the man to look for. Now, have a look there:

http://aminet.net/package/misc/emu/bochs-2.6

The "Uploader" line is the one to focus on, as it contains the email address (and full name as well) of the same guy.
I think you should know now from whom and how to request the source code of the MorphOS port of Bochs 2.6.

Still, I'm very interested in the solution to this "j.vancalrehden" mystery :-)

Update:

Proper person is now emailed.
Waiting....

Update:

XP installed fresh and is working.
Speed is not all that bad on a Powerbook 5,9.
I bumped the screen res from 640x480 to 1024x768 and got multiple errors.
I am going to bump to 800x600 next time and see if that goes ok.
Going to check the device manager and set the Desktop for best performance (no special effects).



[ Edited by bash64 11.05.2013 - 09:56 ]

Update:

I have xp installed and using (2) 2gb drives with the paging file on drive D:
I will be zipping up the whole folder and making it all available for download via ftp server sometime monday or tuesday.
xp is as optimized as it can get and running in 800x600 mode.
Everything not necessary has been turned off and , well, on a powerbook 5,9 it runs fairly well.

Update:

Its a definite, 800x600 is the max. 1024x768 crashes the emulator.
I tried using a different video bios (the cirrus one) but that led to 4 bit color and then to a crash.
When I added the 2nd hard drive the cdrom disappeared.
It appears to be a 2 drive limit for bochs. Doesn't matter what controller you put them on, you can definitely have 2 controllers, but if you break the 2 drive limit the 3rd drive does not show up anymore.
All of the plugins are missing with bochs.
Really need to get those compiled.

Hey,

I downloaded a windows xp logo in png format.
I want to make that the icon for bochs.
How do I do that?
Thanks

Rename it to Bochs.info

I did this before I asked for help but it took till later on for Ambient to recognize the .info pong and display the icon.
Anyway, When I double click on the bochs.info (renamed .png file) ambient does not launch bochs.
What gives?

Update:

I have switched to reading "C, the Complete Reference - Herbert Schildt".

Way better book.

I still have no response from the developer for bochs 2.6.
I would appreciate it very much if a few of you would try to email him also.
Please ask for the source code for the MOS version (should be 2.6).
Plus any experimental coding for the plugins like the NIC.
Thanks

@bash64

I forwarded your email address to Thore.