Partition Cluster Size.

[Control Freq]

Further to my problems with "SYSTEM_LICENSE_VIOLATION" Problems.

It has been suggested that my problems are due to:
1) Incorrectly entered PID key.
2) Wrong Partition size.
3) Not installing SP2 properly.

I have reinstalled everything, and still get the same problem.

However, I am using a partition size of 500MB. I use a Win98 boot
diskette to boot my embedded computer system, and I use the fdisk on
it to create a bootable 500MB FAT16 partition accordingly.
I was wondering what should be the correct cluster size (bytes) to use
in the Target Designer.

I have 4096, but is this correct for FAT16?


Thank in advance.

Regards

 

[JS]

- Does the system boot when no PID is entered?

- Is the partition you are creating the first partition on the drive?
(ie there are no other partitions or drives involved)

- A wild guess: try using a partition size of 512. I believe partition
utilities round off the partition size to fill out an entire logical
area of the drive.

- Another guess: try FAT32

 

[Control Freq]

- Does the system boot when no PID is entered?
Yes.


- Is the partition you are creating the first partition on the drive?
(ie there are no other partitions or drives involved)
Yes.


- A wild guess: try using a partition size of 512. I believe partition
utilities round off the partition size to fill out an entire logical
area of the drive.

Ok, I will try that.

- Another guess: try FAT32

I tried FAT32, but I got a bootup message saying "Non system disk, or
disk error" Or something like that. I then tried FAT16 and that
particular problem went away.


Thanks for the advice.

Regards.

 

[Control Freq]

Well, my problems were several, and the solutions were unrelated.

Firstly, I had to ensure that SP2 of the dev tools was correctly
installed. This required quite a lot of uninstall/reinstall to get it
setup right.
Secondly, Don't use 512 MB partition. It doesn't work (or not on my
hardware anyway). 500MB works fine.
And FAT32 doesn't work for me either, FAT16 is OK.

I hope I don't have to go through XP Embedded install again. It took 5
working days to get this job done.
The main problem is that the dev tools don't install correctly out of
the box.
However, it has been suggested that my problems were caused by playing
with the evaluation downloads before the proper stuff arrived on
CDROM.
If I had waited for the CDROMs to arrive then I might have saved the 5
days of headache later!!!

Regards