Quote:

SymbOS needs to be copied to the root dir (A:\) of the 4th (windows) partition, which is the 1st MSX partition if you use fdisk310 which you get with you Sunrise IDE/CF.

Huh? Sorry, I'm completely not following you. What is a windows partition, and what is it doing on an MSX harddisk? I thought Windows uses NTFS and VFAT as file systems. Do you mean you have three of those on your MSX hard disk?

I did partition my MSX harddisk using the latest version of Sunrise's fdisk, I think I downloaded it when I started playing with FAT16, so it should be fairly recent.

Anyway, putting Symbos and its apps directory in the root of the first partition (a:\) didn't solve it.

Partitions (1, 2, 3, 4, etc) are not filesystems (ntfs, fat12, fat16, fat32, ext2, reiserfs, etc). You can make partitions on practically any OS (I made mine with linux, because I couldn't get sunrise fdisk310 to make partitions smaler than 32MB)
I then formated my 4 linux-made partitions on my MSX again.
If you partition a disk or CF-card with sunrise's fdisk310, it created the partitions in a different order then when created on windows or linux. So 'partition 4' where everybody is talking about, is the fourth partition in windows or linux counting and not as it would be made with sunrise's fdisk310.
I hope I'm making sense this time

Quote:

I hope I'm making sense this time

Yes, you are. So how do I find out what partition to use on my MSX?

BTW On *nix systems the word file system frequently does refer to partitions, when people talk about the /var, /boot or /home file systems, for instance.

Quote:

Prodatron, yes, I was asking for "System Security", that I saw at last BCN PARTY in Silenci's CPC 6128. It was very curious. Also, I've seen a "lock" and "unlock" feature, as you can see in the photo I took from the same CPC: http://www.perugorria.unlugar.com/bcn101/073.JPG As I see it was included on "System Security". You're right that being out of the core of SymbOS is better for memory, but it's good to know that it will be also a module-app Finally, a stupid thing ^^, change SymbOS CPC names to SymbOS MSX when you can PS: Enjoy the VG8235. My MSX is a MSX 2 VG8235 with 2DD disk drive (which was put on my MSX by Padial in December 2002) and it's totallly great, as most of Philips MSX are.

Erm, yes, of course I will replace it with "MSX" soon I already changed the version string and system type byte, so that control panel -> system shows the correct information, but I have to modify the graphic, too.
The current version of SymbOS is already prepared for this "system security" module (you can activate it in "control panel -> system", I just need to put the form data and sources together again as an application.
I like the VG8235 a lot, seems, that it was one of the most sold MSX2 here in europe, as I saw it quite often on Ebay. Flyguilles hint with the commodore monitor was very useful, now I have a perfect razor-sharp picture. Hope I can also replace the drive with a double side one somewhen in the future.

Regarding partitions: Right, seems, that for MSX the forth entry in the MBR is the first one. I will implement an automatic detection later, and when disc support is running, you can start the control panel from disc and configure the correct partition there manually.

diederick76:

Quote:

So how do I find out what partition to use on my MSX?

The way I did it, was partition my 32MB CF-card in 4 primary partitions of 8MB (on linux) and then use MSX's fdisk310 to 'enable' them all. The first MSX partition (the 'A:' drive) was a little smaller then then rest, which was precisely the last/4th partition I created on linux.
So I knew that I had to use this partition

diederick76:

Quote:

BTW On *nix systems the word file system frequently does refer to partitions, when people talk about the /var, /boot or /home file systems, for instance.

Well, even you said "/var, /boot or /home file systems" and not "/var, /boot or /home partitions" But as on linux most filesystems and partitions are created one-on-one I can see the confusion. (note that on bigger unix rigs this is often not the case. they create a big partition, and use LVM to create multiple logical volumes, each with their own filesystem)

I'd call /var, /boot, /home, etc. mount points. They can be, at least. So, you could mount a partition on /var and have all /var stuff on that separate partition.

In general, a file system is a formatted/initialized (logical) partition or volume, with a type of something like ext2, ext3, reiser, fat32, ntfs, hpfs, etc.

AFAIK LVM is using multiple disks for one virtual partition (a logical volume), not the other way around (see: http://en.wikipedia.org/wiki/Logical_volume_management )

Anyway, this is all quite off-topic I suppose

Hm, I don't have a CF card (I bought the Sunrise IDE interface immediately when it was available (how long is it ago) before they made CF cards. I'm not very eager to shut down and open up my Linux box to format a hard drive. Is there a way I can create a suitable partition using my MSX and how big should it be?

manuel wrote:

Quote:

AFAIK LVM is using multiple disks for one virtual partition (a logical volume), not the other way around (see: http://en.wikipedia.org/wiki/Logical_volume_management )

You can concatenate multiple disks into a volume group with 'vgcreate' and convert them into multiple logical volumes (each with their own filesystem) with 'lvcreate'. all these tools (pvcreate, vgcreate, lvcreate, etc) are part of LVM. So we're both right

manuel wrote:

Quote:

Anyway, this is all quite off-topic I suppose

Pretty much

diederick76 wrote:

Quote:

Is there a way I can create a suitable partition using my MSX and how big should it be?

I would suggest (if possible) to repartition your entire drive with MSX/fdisk310, 'kill' all but the first 4 partitions, initialize them, put DOS and SymbOS on your A:\ drive and all SymbOS apps in A:\APPS\
I don't think size matters so you can make them as big or small as you want.
Ohw, this is all just a suggestion, so don't blame me if it doesn't work

Patsie: I tried that on a harddrive, and it didn't work. Error code 02 Works better on my CF though. But I only get task manager, calendar and info running.

Seems like the problem on openMSX isn't a bug in openMSX after all. It also occurs on real hardware. Maybe a timing problem? Different hardware might have slightly different timing, making some tightly timed routines fail?

Please check that Prodatron!

Manuel: Exactly my point earlier in this thread. If he get's it to work in openMSX it will have a much better chance of working on my setup.

manuel, I checked the openMSX ide emulation and it looks like you don't emulate the READ NATIVE MAX ADDRESS ata command. If you at least don't set the error bits when the command is issued I'm pretty sure SymbOS will start working in openMSX.

Just add the following case in AbstractIDEDevice::executeCommand :

	case 0xF8: // Read Native Max Address
		// ignore command
		break;

yes, this does make it work indeed! Thanks dvik! Oh, and if you find more IDE (or other) bugs or missing stuff, you know where to find us