Forum Replies Created
-
Posts
-
You use the following syntax:
import_entity rom1(“rom1.vhd”);
From now on you can use the “rom1” entity as if it was implemented in THDL++.
Note that this feature is experimental and will most likely not work with complex entities (e.g. having generic-dependent ports). However, it works for Xilinx generated cores.OK, which example are you trying and what entity are you trying to visualize? Are you using “Project->Visualize” command, or “Visualize entity” command from the context menu? If you modified the example, ensure that one of your source files contains something like that:
//The following line will take effect when building simulation model
simulate_entity(SimulatedClockProvider<20ns, LEDBlinkDemo>);//When using VisualHDL with Xilinx tools, VisualHDL will build the
//FPGA bitstream file automatically based on the following line:
synthesize_hardware<"xc3s700an-fgg484-4"> LEDBlinkDemo(
clk=”E12″,
LEDs=”W21,Y22,V20,V19,U19,U20,T19,R20″
//The post_route_sim statement is optional and is only used for generating
//post-route simulation models.
) post_route_sim(SimulatedClockProvider<20ns, LEDBlinkDemo>);This essentially means that if you’re building a simulator configuration (selected on top of the project file list), the root entity will be the one specified by simulate_entity. Similar for FPGA builds.
Don’t believe the message about “generate_vhdl”, it was not updated since the build when generate_vhdl split into simulate_entity for simulator builds and synthesize_hardware for FPGA builds. Will fix the msg in future versions.
Please search for GearASPIWdm on this forum.
If you want any other mounting software to work, simply reinstall it, so it updates file associations.LGPL. Basically, yes. If your company adds some more features to its customized version of WinCDEmu, you will have to publish the updated sources. If you don’t touch the sources, there are absolutely no restrictions on use cases.
The link is not working (says “disable your adblock software to download”). Please register at the forum and use the ‘upload file’ function.
Guess what happened after I clicked “Uninstall Driver” …? *correct* the driver was uninstalled. But the one that was on the system before… :-/
Are you absolutely really sure? This is very wierd. The two drivers use totally different installation/uninstallation mechanisms. Could you describe, what made you believe the wrong driver was uninstalled? Maybe, there are some CDROM class filters tampering around?
The idea is fine, but still one has to have admin-rights (yes, I know, because of the driver-issue).
Well, this is beyond my powers. You need to be an admin to install drivers and you need to install the drivers to add virtual devices. If you need a ‘non-admin’-portable way of accessing ISO files, use 7-zip or any other archiver that would just extract it on your disk, or a file manager with an ISO parsing plugin.
Your problem is caused by a buggy filter driver. Please read this post: viewtopic.php?f=3&t=517
Thought about it. Drag-n-drop won’t work through UAC. A non-privileged application (e.g. Explorer) cannot send a message to a privilleged application (WinCDEmu mounter). WinCDEmu mounter cannot remain unprivilleged, as it needs to install and access the kernel driver.
As for the other features, I’ll see what I can do, but it won’t be very soon, as I don’t currently have much time to spend on the project.
Anyway, thanks for the feedback.I believe you have some buggy CDROM class filters. Search for GearASPIWdm on this forum. If you do not find a solution, please post again.
The incompatibility caused by GearASPIWdm is a known issue. If you prefer calling WinCDEmu buggy rather than searching the forum for a solution, it is your choice.
To remove the “Select drive letter & mount” prompt, please go to the HKCR.iso key, look up the default value there (e.g. BazisVirtualCD.Iso), then go to HKCR{value from .iso}shell and remove the “Select drive letter && mount” subkey.You can remove any unusable program, as well as any usable program by using “add/remove programs” applet in the Control Panel.
Additionally, I would recommend checking for buggy 3rd-party CDROM filter drivers (search this forum for GearASPIWdm). They might be the reason of WinCDEmu being unusable on your machine.Did you select “never install non-WHQL-signed drivers” in your system settings?
WinCDEmu now has a signed kernel-mode driver, but it was obviously not WHQL-certified.Done. Check out the beta here: http://wincdemu.sysprogs.org/portable
If you can find a detailed description for those formats, I will consider supporting them. Otherwise, analyzing an unknown binary format is quite a hassle and is questionable unless the format is really popular. You can also provide your own implementation based on WinCDEmu format driver interface, so I will include it in future versions of WinCDEmu.
I guess, you can use devcon or other Microsoft tools to cleanup drive information as well. Anyway, do such leftovers cause any real inconvenience to anyone? Windows is designed to keep history of all previously connected devices, this information does not occupy any considerable amount of your disk space or RAM and does not slow your system…
