02-27-2012 08:31 AM
When using the Create PC Format Disk options on MAX to make a floppy disk that should allow formatting a hard disk on a LabWindows/CVI real time target, there is a big problem when the target only has a USB Floppy drive available.
Even though the system indeed boots from the floppy and indeed starts the "Desktop PC Hard Drive Format Disk" program, actually doing some reinitializing of the hard disk (or in this case compact flash disk playing the role), the display shows many times "Warning KERNEL.346530: Error initializing Floppy drive A:" and eventually fails to open source file hdmon.bin (which actually does exist on the floppy).
It seems that once ETS Loader takes over, it does not know that the drive A: is not a real floppy drive.
Is there a version of the utility that does NOT try to access the floppy drive through a real floppy drive controller?
It also seems that the reinitializing of the disk was also not successfully completed; copying the necessary file to the disk afterwards does NOT make the disk bootable for LabWindows Real-Time.
Is there maybe some PC utility that allows building a bootable compact flash, similar to HP USB Formatter for DOS bootable disks? This really would remove a lot of hassle.
03-06-2012 05:25 AM
Hello,
Thanks for your posting in this forum. I think that you can use the link below which is related to your issue.
http://force.natinst.com:8000/pls/nic3/niae_screenpop.main?p_incident_number=1544235
I hope that it could be useful and if you have any question, don't hesitate to ask me on this forum.
Regards,
Hossein
08-01-2012 06:27 AM
Hello Hossein,
Thanks for your attempt to be helpful, but sadly the link you provided only leads to unavailable webpages here. force.natinst.com cannot be resolved into an IP address from here and I checked various DNS loopup services online who all report that nameservers ns3.natinst.com and ns4.natinst.com do not know force.natinst.com.
Sorry for not having replied sooner.
I am still looking for a solution though.
Aart.
08-01-2012 07:13 AM
Hi,
Thanks for your reply. I think that this link will work.
http://digital.ni.com/public.nsf/allkb/7E0612D6C15BE1AD8625723B005E579E?OpenDocument
Regards,
Hossien
08-01-2012 09:36 AM
Hello Hossein,
The USB stick boots into Win98(DOS), that's good.
But it's the 8.5 RT Disk Utilities that I want to run from that USB stick and the bootloader of the stick only loads IO.SYS and not diskmon.bin or hdmon.bin.
grumble, grumble
thanks for the help so far though.
08-06-2012 08:37 PM
I am a little confused about what your eventual intent is, so I will ask a couple questions that will hopefully lead you to success faster.
-Danny
08-08-2012 09:32 AM
Thanks for your input Danny,
Despite being able to run the utility disk I still get trouble:
One time I got a succesfully reliance formatted flash disk, that also booted on its own, but reproduction of that result is very hard. Like within the same setup just getting another flash disk with a little more capacity the formatting gave me the error again.
Apparently there are many variables involved.
Maybe you or anyone else can come up with some procedure that has a 100% success rate.
08-08-2012 10:01 AM
Hi,
I found this error in the other forum post and the solution was:
All references to those Kernel errors appear to be CARs that have not been reproducible, or problems specific to hardware in the RTPC. Unfortunately, the Real-Time Module PC Evaluator is not exhaustive: sometimes it reports success when there is still an issue with the hardware being used. Since the typical formatting and installation of software has failed, I recommend the following:
1) Pull out the Hard Disk and format it in FAT32 using another formatting tool. This will require setting up the hard drive as a secondary hard drive in a Windows machine and then formatting it in FAT32.
2) Copy the contents of a working RTPC hard drive to the newly formatted hard drive.
3) Place the harddrive back in the RTPC and boot it.
This should effectively apply the generic RTPC image to the customer's hard drive. If this still fails, then there is most likely a hardware issue. In the future I would recommend customers use a configuration from this (https://decibel.ni.com/content/docs/DOC-10692) document.
Hope this would help.
Regards,
Hossein
08-08-2012 12:26 PM
You're right, you've got multiple issues going on.
The RT PC Desktop USB Utility I pointed you to is your best bet - it has all the latest driver updates for RT, if that doesn't help you get to a point where you can boot your PC104 system reliably, I don't think anything can.
-Danny
08-22-2012 02:24 AM
I have finally got a reproducable bootable reliance 128MB flash disk creation procedure for my specific situation.
The CPU used is a Versalogic Manx (VL-EPM)
BIOS setting for flash disk (IDE0) type Physical (LBA did not seem to work on this system for my disks)
(Master or Slave makes no difference, both can work)
It works for a InnoDisk iCF 4000 128MB disk, but not for a InnoDisk iCF 4000 512MB disk, nor for a InnoDisck iCF 2000 128MB disk (Error -1: unknown I/O write error when trying to format).
None of these disks could be formatted in FAT and booted afterwards on their own.
A USB Utility disk created with a recent Measurement & Automation Explorer (version 5.3.1f0) does not boot properly (constant rolling error message of unrecognized OHCI device).
A USB Utility disk created using http://joule.ni.com/nidu/cds/view/p/id/2700/lang/en as suggested by Danny does boot properly and helped creating a working InnoDisk 4000 128MB disk with reliance.
It is clear that creating a bootable disk is very not straight forward, although you might think it is just putting the right bytes in the right sectors on the flash disk and you should be able to create a working disk with any flash card reader on any PC (provided admin access granted).
The biggest problem is possibly that not all flash disks report their geometry properly (assuming that access will be done through LBA) all the time through the IDE interface and that pseudo CHS settings do not always match the physical sizes even if the size of the disk falls within CHS limits. Some of this might even apply to USB memory sticks that need to be booted from.
When I or someone else (preferrably some NI personnel) has some spare time, analyzing the reliance boot sector code (MBR and OS Boot sector) could maybe lead to a general utility that runs on a PC with a flash card reader, where possibly different CHS geometries can be tried.
Thanks to all for your input so far.