NoWind - update regarding support & documentation

Page 2/2
1 |

By yzi

Champion (444)

yzi's picture

16-08-2011, 20:54

I think it's possible that the problem has something to do with exact library and/or compiler and/or operating system versions.

Jan: can you put your compiled Mac and Linux binaries somewhere so we could try those?

What kind of info could we provide about our systems? I'm using Mac OS X 10.6 "Snow Leopard", Xcode 3.2.6 64-bit (Xcode Core: 1809.0 and ToolSupport 1806.0) and the newest MacPorts stuff (CMake etc) available at the time.

By Marq

Champion (387)

Marq's picture

17-08-2011, 20:55

Victory! Seems to work with MSX1/DOS1 now. I downloaded the http://nowindlibraries.googlecode.com/svn/release_aug_2011 version of the source, flashed the cartridge, compiled nwhostapp and it seems to work like a charm at least on Canon V-20 and Toshiba HX-10. Somehow I get the feeling that the previous firmware only had DOS2 BIOS on it, while this new one only has DOS1, since my MSX2 didn't care anything about the -2 flag.

Edit: In hindsight dos2 might work better if the disk images had such thing on them :) At least disk basic version seems to change to 2.01 with the -2 switch.

By yzi

Champion (444)

yzi's picture

17-08-2011, 21:22

Great! Now we can finally rest this case.

By Manuel

Ascended (18256)

Manuel's picture

17-08-2011, 23:06

That sounds more like it (and like my good experiences with this thing). Enjoy!

By Sky_hawk

Champion (267)

Sky_hawk's picture

20-08-2011, 07:27

yzi, just to make the story complete, I've taken a look at your MSX1 output and I can definately say that the BDOS patch was ON in that firmware you are using. That means you cant insert any 'DOS' disk images because all bdos calls are being re-routed and never get to the nowind-diskrom.
This is also why you see the content of the host-directory when you use 'files'.

At this moment only bdos open file and random block read are 'sortof' working, so not much software actually works yet.
(the feature is just not finished yet).

HOWEVER, if you inserted a disk that uses only sector-based access (like ALESTE2) the bdos is never used and everything would appear normal.

This might explain some of the weird behaviour you were seeing.

Greetings,

Jan (btw. on a totally unrelated note: I just because the father of an 'Anouk' on 17 August 2011)

By Sky_hawk

Champion (267)

Sky_hawk's picture

20-08-2011, 07:30

yzi, great, I seems the new firmware release solved you problems Smile We disabled the BDOS patch and improved automatic error-handling in case of wrong use of commandline switches for MSX1 and Turbo-R.

Greetings,

Jan

By Huey

Prophet (2677)

Huey's picture

20-08-2011, 10:12

the father of an 'Anouk' on 17 August 2011)

Congrats!!!

By Sky_hawk

Champion (267)

Sky_hawk's picture

21-08-2011, 20:27

Btw, please report any non-working hardware or features as issues in http://code.google.com/p/nowindlibraries/issues/list

By Sky_hawk

Champion (267)

Sky_hawk's picture

23-08-2011, 09:53

Now that I've become a father I realize even more that time will be limited commodity for a while (the coming 21 years? Smile
I've come to the conclusion that more nowind developers are needed to continue regular updates.

Until now this was very difficult, sometimes, even between the two of us.
We went through several difficult redesigns in the firmware source code, but now, it is becoming more and more stable,

First of all we are looking for developers willing to write MSX DOS 1 and 2 utilities for the nowind interface. We provide an API and support to access to Nowind Interface from a high level point of view. Functions like 'find nowind interface slot' and 'change image' are available, what we need is people to write DOS utitilies that make use of this API and make it 'user friendly' while we provide the technical support and continue work on the core features. You wont has to start from scratch, we have some basic working examples and ofcourse we will help getting you started. Also we provide a comfortable emulation environment that will allow you to develop en test code without an actual nowind interface or MSX if desired. Ofcourse you can also choose to test using real hardware, its up to you.

Interested? Let us know.

Greetings,

Jan

Page 2/2
1 |