XC8 1.44编译器试图访问软盘驱动器A

这已经出现了，但我不知道是否有一个解决方案是一致同意的。HTTP//www. McCHIP.COM/FUMMS/M1015934.ASPXA卸载/重新安装MPLAB X可能会有帮助，但我认为它对那个线程中的人不起作用。



      以下为原文

    This has come up before but I don't know if a solution was ever agreed upon.
http://www.microchip.com/forums/m1015934.aspx
A uninstall/reinstall of MPLAB X might help but I don't think it worked for the person in that thread.

这个问题更可能是MPLABX而不是XC8。确保驱动器A不在系统路径或项目路径中。



      以下为原文

    The issue is more likely MPLabX than XC8.
Make sure drive A is not in the System Path or in the project path.

嗨，如果你不使用软盘，就在BIOS中禁用它。你的电脑也会启动得更快。



      以下为原文

    Hi,
If you don't use the floppy, just disable it in the BIOS.
Your PC will also boot faster ;=)
Regards

BIOS禁用解决当然问题，但我随便使用软盘（是2017，因为我的7000美元TEKTRONICK TDS3052范围存储屏幕上的截图）。现在不想再买别的东西了。



      以下为原文

    BIOS disable solves the issue of course, but I use the floppy casually (YES in 2017, because my 7000 $ Tektronik TDS3052 Scope stores screenshots to floppy disk). Don't want to buy another scope now.

我在同一个船坞：，必须保持软盘驱动器周围的一个传统的DoS 6.22为基础的系统，我的公司来的是，我需要更新代码/做维护。一旦我禁用驱动器，将不可避免地出现在那一周。



      以下为原文

    I'm in the same boatgrin: , gotta keep the floppy drive around for that one legacy DOS 6.22 based system my company makes comes in that I need to update code/do maintenance on.  As soon as I disable the drive one will inevitably show up that week.

正如我所说的那样，许可证管理器（XCLM）已经被报告导致软盘访问，即使它非常明确地跳过A:和B：当寻找一个软件狗。MPLAB X直接运行XCLM，寻找许可信息在仪表板中显示，编译器每次启动时都运行XCLM，所以如果你在XCLM调整你的软盘驱动器的情况下，你肯定会看到很多这样的访问。我现在已经检查了XCLM源：它走到窗口。S注册在“StaleStimeDeaveStudioDoStices”下，查找当前活动磁盘，如您所见，它跳过“A:”和“B:”。您应该能够通过运行XCLM自己（它在编译器的bin目录）中找到它的命令行选项——东信息3——您会看到许多诊断信息被打印出来，但是这里的相关部分将是上述两个消息的任何实例。如果你打开一个支持的例子，附加一个完整的输出的拷贝和粘贴加上一个到这个线程的链接，我可以被分配时间来跟踪并消除它。



      以下为原文

   
As I said elsewhere the license manager (XCLM) has been reported to cause floppy access, even though it very explicitly skips A: and B: when looking for a dongle. MPLAB X directly runs XCLM looking for license info to display in the dashboard, and the compiler runs XCLM every time it is fired up, so if you're in the situation where XCLM tweaks your floppy drive you will certainly see many such accesses.
 
I've now checked in the XCLM source: it walks the Windows Registry under "SYSTEMMountedDevicesDosDevices" looking for currently-active disks, and as you see hereif ((toupper(mounted_device[0])=='A' || toupper(mounted_device[0])=='B') &&
mounted_device[1]==':' && mounted_device[2]==0) {

    if (verbose > 1) printf("Skip (floppy) device %cn", mounted_device[0]);

    i++;

    continue;

}

if (verbose > 2) printf("Mounted device [%s] foundn", mounted_device);
it skips "A:" and "B:". You should be able to see what it is finding by running XCLM yourself (it's in the compiler's BIN directory) with the command line option -dongleinfo 3 - you will see a lot of diagnostic info printed out, but the relevant parts here will be any instances of the above two messages. If you open a support case attaching a copy-and-paste of the full output plus a link to this thread, I may be allocated time to track this down and eliminate it.

H和以上是我的读卡器



      以下为原文

    H and above are my card reader
   Attached Image(s)

这就是我所显示的：C:程序文件（x86）Microchip xC8v1.44 bin；gt；xClm -东莱文信息3 -ClxsSpReSeSEC＝1000 { 10 }，在枚举AtHytPositStutsDutoDebug设备[DuxStutsC:] FunDo.DoDeStudioTube设备注册值中预期[]卷{0602B03-D2DE-11E3-A2B3-806E6F6E6963}[No.Doices设备]在安装设备注册值中期望[]？？卷{{B0602B04-D2DE-11E3-A2B3-806E6F6E6963}〕无需DOTS设备，在安装的设备注册表值中期望[]？？卷{{B0602B07D2DE-11E3-A2B3-806E6F6E6963}〕无需DOTS设备。？卷{{B0602B08D2DE-11E3-A2B3-806E6F6E6963}]安装的设备[Debug StudioA:] FunDo.DoDeSosits，在安装的设备注册表值中期望[]？卷{A7F0CA8D2E1-11E3-8E54-806E6F6E6963}[No.Doices设备]在安装设备注册值中期望[]？卷{A7F0CA9D2E1-11E3-8E54-806E6F6E6963}[No.Doices设备]在安装设备注册值中期望[]？卷{{A7F0CA1-D2E1-11E3-8E54-806E6F6E6963}[]安装的设备[DOSMODEsF:]基础安装的设备[Debug StudioG::FunDo.DoDeNoSts ]在安装设备注册值中预期[]？卷{{13A15EA8D424 11E3-91C0－019DB628 A9}}安装的设备[Debug StudioH:] FunDo.DoDeNoSts，在安装的设备注册值中期望[]？卷{{B3DBD351-D510-11E3-8B28806E6F6E6963}[]安装的设备[Debug StudioD::FunDo.DoDeStudio]，在安装的设备注册值中期望[]？？卷{{3B940314-D5E-11E3-84C0－019DB628 A9}}安装的设备[Debug StudioE::FunDo.DoDeNoSts ]在安装的设备注册表值中期望[]？？卷{{8D81434-D68 1-11E3-84C5-019DB628 A9}}没有安装在设备的注册表值[]的DoDebug设备。卷{{8D8143A D68 1-11E3-84C5-019DB628 A9}}安装的设备[Debug StudioI:] FunDo.DoDeNoSts，在安装设备注册值中期望[]？？卷{{7D73098DB4B-11E3-844 3-019DB628 A9}}没有安装在设备的注册表值[D]中的DOX设备。卷{FE0A7F73-F5EA11E3-A31-019DB626A9}[NODISODATION]在安装设备注册值中期望[]？卷{FE0A7F75-F5EA11E3-A31-019DB626A9}[NODISODATION]在安装设备注册值中期望[]？？卷{{4242B5964C6711E4-A9A0－05056C000 }}没有安装在设备安装注册表值中的[DUSEDATION]设备[]？卷{{E56F3B85-933 4-11E4-A0E0-019DB628 A9}}[No.Doices设备]在安装设备注册值中期望[]？？卷卷{162DCE93-B9C811E4-81D2-806E6F6E6963}[NODUSEDATION]在安装设备注册值中期望[]？？卷{{6D589FD3-BAAB-11E4-81D8F81A670B792B}[]没有DOTS设备，在安装设备注册值中期望[]？卷{{1717DFFA8B911E5-9D8E-019DB626C14}安装的设备[DOSMODESJ:] FunDo.DoDeSosits，在安装设备注册值中期望[]？卷{C520585-8F8B-11E5-9D95-019Db9B5311}[NODISODATION]在安装设备注册值中期望[]？卷{0C98BC599432-11E5-8032-019Db9B5311}[No.DoDeStudio]在安装设备注册值中期望[]？？卷{{3EEA0131-B8C-11E5-82E3-806E6F6E6963}〕无需DOTS设备。卷{6E31 B9D6C4EA 11E5-AF27—019DC1A1355 }没有安装在设备寄存器值中的[DOS]设备[]？卷{096D60D0F4-11E5-B6B-806E6F6E6963}[No.Doices设备]在安装设备注册值中期望[]？？卷{{BB8AE6BB-0943-11E690-1519-DC2B41B}}[NODUSEDATION]在安装设备注册值中期望[]？？卷{{8A15B660BE-11E7A8A7—019DDC63A5}[]无DoDeStudioMULTED设备注册表值中预期[]？卷{59FCFB65-5E-11E7BB9F-019DDC63B26}[NODUSEDATION]在安装设备注册值中期望[]？卷{02061A7B-5FBF 11E79DBE-019DDC63B26}[NODUSEDATION]在安装设备注册值中期望[]？？卷{{4B13D51-6D8911EB-BB23-019DDC63B26}[NODISODATION]，在安装的设备注册表值中期望[]？卷{37 BEAE73-8891-11E7BE77.19DDC7B28 }没有安装在设备注册值中的[DoDeDebug ] [？？卷{{E7B2D8F6B0D2-11E7BE39－019DDC7B29 }〕NO.DOWS设备在安装的设备注册表值中期望[]？？卷{{8FCD843B892-11E7990B-1919DDC7B29 }〕无需DoDebug设备在安装设备注册值中期望[]？在枚举AtSerialNoMalSerServer打开注册表项“StaseCurrnCuttoStutsServsUbStor EnUm”之前，在枚举安装点{ 30 }后，卷{{8FCD843E-B92-11E7990BDD2-919DDC24B29 } { 30 }：WASKLIXESESEX文件之前枚举序列序号{ 30 }后的DASStEngEnKeNe DATEI NICHT FUNDEN { 30 }在WalkuLiceNeSexFielsC之后的S PrrtTeNeLeIX许可证{ 30 }：程序文件（x86）Microchip xC8V1.44 bin·Gt；



      以下为原文

    This is what I get displayed:
 
C:Program Files (x86)Microchipxc8v1.44bin>xclm -dongleinfo 3 -
CLOCKS_PER_SEC=1000
{10}before enumerate_mountpoints
Mounted device [DosDevicesC:] found
No DosDevices where expected in MountedDevices registry value [??Volume{b060
2b03-d2de-11e3-a2b3-806e6f6e6963}]
No DosDevices where expected in MountedDevices registry value [??Volume{b060
2b04-d2de-11e3-a2b3-806e6f6e6963}]
No DosDevices where expected in MountedDevices registry value [??Volume{b060
2b07-d2de-11e3-a2b3-806e6f6e6963}]
No DosDevices where expected in MountedDevices registry value [??Volume{b060
2b08-d2de-11e3-a2b3-806e6f6e6963}]
Mounted device [DosDevicesA:] found
No DosDevices where expected in MountedDevices registry value [??Volume{a87f
0ca8-d2e1-11e3-8e54-806e6f6e6963}]
No DosDevices where expected in MountedDevices registry value [??Volume{a87f
0ca9-d2e1-11e3-8e54-806e6f6e6963}]
No DosDevices where expected in MountedDevices registry value [??Volume{a87f
0caa-d2e1-11e3-8e54-806e6f6e6963}]
Mounted device [DosDevicesF:] found
Mounted device [DosDevicesG:] found
No DosDevices where expected in MountedDevices registry value [??Volume{13a1
5ea8-d424-11e3-91c0-0019db628a91}]
Mounted device [DosDevicesH:] found
No DosDevices where expected in MountedDevices registry value [??Volume{b3db
d351-d510-11e3-8b28-806e6f6e6963}]
Mounted device [DosDevicesD:] found
No DosDevices where expected in MountedDevices registry value [??Volume{3b94
0314-d54e-11e3-84c0-0019db628a91}]
Mounted device [DosDevicesE:] found
No DosDevices where expected in MountedDevices registry value [??Volume{8d87
1434-d681-11e3-84c5-0019db628a91}]
No DosDevices where expected in MountedDevices registry value [??Volume{8d87
143a-d681-11e3-84c5-0019db628a91}]
Mounted device [DosDevicesI:] found
No DosDevices where expected in MountedDevices registry value [??Volume{7d73
0978-db4b-11e3-8443-0019db628a91}]
No DosDevices where expected in MountedDevices registry value [??Volume{fe0a
7f73-f5ea-11e3-a331-0019db628a91}]
No DosDevices where expected in MountedDevices registry value [??Volume{fe0a
7f75-f5ea-11e3-a331-0019db628a91}]
No DosDevices where expected in MountedDevices registry value [??Volume{4242
b596-4c67-11e4-a9a0-005056c00008}]
No DosDevices where expected in MountedDevices registry value [??Volume{e56f
3b85-9334-11e4-a0e0-0019db628a91}]
No DosDevices where expected in MountedDevices registry value [??Volume{162d
ce93-b9c8-11e4-81d2-806e6f6e6963}]
No DosDevices where expected in MountedDevices registry value [??Volume{6d58
9fd3-baab-11e4-81d8-f81a670b792b}]
No DosDevices where expected in MountedDevices registry value [??Volume{6817
dffa-28b9-11e5-9d8e-0019db626c14}]
Mounted device [DosDevicesJ:] found
No DosDevices where expected in MountedDevices registry value [??Volume{c520
5285-8f8b-11e5-9d95-0019db9b5311}]
No DosDevices where expected in MountedDevices registry value [??Volume{0c98
bc59-9432-11e5-8032-0019db9b5311}]
No DosDevices where expected in MountedDevices registry value [??Volume{3eea
0331-b88c-11e5-82e3-806e6f6e6963}]
No DosDevices where expected in MountedDevices registry value [??Volume{6e31
b9d6-c4ea-11e5-af27-0019dc1a1355}]
No DosDevices where expected in MountedDevices registry value [??Volume{d096
d670-d0f4-11e5-b66b-806e6f6e6963}]
No DosDevices where expected in MountedDevices registry value [??Volume{bb8a
e6bb-0943-11e6-9015-0019dc2b441b}]
No DosDevices where expected in MountedDevices registry value [??Volume{87a1
5b66-0bbe-11e7-a8a7-0019ddc63a51}]
No DosDevices where expected in MountedDevices registry value [??Volume{59fc
ffb6-564e-11e7-bb9f-0019ddc63b26}]
No DosDevices where expected in MountedDevices registry value [??Volume{0206
1a7b-5fbf-11e7-9dbe-0019ddc63b26}]
No DosDevices where expected in MountedDevices registry value [??Volume{45b1
3d51-6d89-11e7-bb28-0019ddc63b26}]
No DosDevices where expected in MountedDevices registry value [??Volume{37be
ae73-8891-11e7-bec7-0019ddc74b28}]
No DosDevices where expected in MountedDevices registry value [??Volume{e7b2
d8f6-b0d2-11e7-be39-0019ddc74b29}]
No DosDevices where expected in MountedDevices registry value [??Volume{8fcd
8438-b892-11e7-990b-0019ddc74b29}]
No DosDevices where expected in MountedDevices registry value [??Volume{8fcd
843e-b892-11e7-990b-0019ddc74b29}]
{30}after enumerate_mountpoints
{30}before enumerate_serialnumbers
Error opening Registry key "SYSTEMCurrentControlSetservicesUSBSTOREnum": Das
 System kann die angegebene Datei nicht finden.
{30}after enumerate_serialnumbers
{30}before walk_license_files print_dongle_license
{30}after walk_license_files

C:Program Files (x86)Microchipxc8v1.44bin>
 
 

谢谢，吉姆-我还没有考虑过像这样的可移动媒体设备的问题。（我有这样一个读卡器，但我不在任何硬件上运行Windows。）从扫描中排除这些设备将进行一些进一步的调查，而我的时间是否会花在其他人身上。



      以下为原文

   
Thanks, Jim - I hadn't considered the issue of removable media devices like that. (I have such a card reader, but I don't run Windows on any hardware here.)
Eliminating such devices from the scan will take some further investigation, and it will be up to others whether my time is spent on that.

谢谢-这表明你的注册表中除了“ASCII”，“A：”存储在那个特定的键，否则你会看到“跳过（软盘）设备”消息，但是存储的任何东西都显示为（ASCII）“A:”，并且指的是软盘设备。也许是非英语系统。M语言设置意味着不同的Unicode字符被存储在注册表中。请记录一个支持这个线程的支持票，并且我会为您找到合适的命令行调用来提取您的注册表的相关部分，以便我可以详细地查看它。



      以下为原文

   
Thanks - this shows that your Registry has something other than (ASCII) "A:" stored at that particular Key, as otherwise you would see the "Skipped (floppy) device" message, but whatever is stored there displays the same as (ASCII) "A:", and refers to the floppy device.
 
Perhaps the non-English system language setting means different Unicode characters are stored in the Registry.
 
 
Please log a support ticket referencing this thread, and I will figure out the appropriate command-line invocation for you to extract just the relevant part of your Registry so I can look at it in detail.
 

马克，谢谢。我已经开了一个支持案例。也许下次你在XCLM，你可能会有时间考虑一下这个问题。



      以下为原文

    Mark,
Thank you.
I have opened a support case.
Maybe next time you are in XCLM you might be allocated some time to have a think on this.