Forum Replies Created
-
Posts
-
@ikas wrote:
Hi..
When I install the version, it first prompts for a path.. then it shows a violet progress bar and instantly it shows a message box with message “Installation aborted”
I go check the folder and i find the following files in that.
.
..
115,200 batchmnt.exe
145,408 batchmnt64.exe
4,843 bazisvirtualcdbus.cat
1,458 BazisVirtualCDBus.inf
langfiles
104,600 uninstall.exe
124,928 uninstall64.exe
197,272 vmnt.exe
258,712 vmnt64.exe
x64
x86 I try using the command line to load files, but it returns me the following message.
Cannot connect to BazisVirtualCDBus.sys: The system cannot find the file specified.I tried copying the sys folder to C:windowssystem32drivers but it still doesnt help.
I run the portable version and it works fine.
Can somebody help me on this ?
I see your point. Usually I just use iso’s, but 7z and zip would’ve been cool. It sucks WinMount isn’t open source, otherwise we could see how they did it without decompression. I have decided to get rid of WinMount, I just realized mounting a 7z file isn’t really worth the trouble having some piece of commercial software around. Maybe you can implement zip/7z mounting later? 😀 😆 What WinMount appears to do is mount it just like an iso, because it never unpacks anything to any temporary directories (or directories period). I’ll bet that could be duplicated, they have an open source floppy mounting program, it uses a lot of the same code as cdrtools. Virtual Floppy Drive, if I remember correctly. I don’t know, it’s a want, not a need. Most people don’t even mount zip and 7z with WinMount anyway…
@Submarine wrote:
this is the messagebox
I got this same error message with:
– Windows 7 (64-bit)
– Vistual Studio 2010
– VisualDDK 1.5.4It works, hope bazis insert this cmd command in the new portable version, is easy but funcional.
When the new version coming out? How knew…Ah, sorry. You might mention in the README.txt that the renaming the old VBoxDD.dll to VBoxDD0.dll is essential and not just for backup purposes. (I named it VBoxDD.dll.bak).
At least the next one having this problem should find a solution on searching 😀
@newGuy3 wrote:
sorry for the tripple post =)
‘Solution’:
(VisualDDk Console) Select: Speed up debugging->Hide all slow windowsafter that it should work, dont know why, but it works….no debug msg anymore!!!
it worked for some minutes, after setting a breakpoint same problem like before -.-…..
sorry for the tripple post =)
‘Solution’:
(VisualDDk Console) Select: Speed up debugging->Hide all slow windowsafter that it should work, dont know why, but it works….no debug msg anymore!!!
@newGuy wrote:
hi guys,
I have the same problem :'(…my specs:
host: win7 x64 sp1
windbg: x86, 6.12…
visual studio 2010guest os: win7 x86
thank you very much =)
another thing: i am using visualddk 1.5.4, virtualkd 2.5.4
when I am trying to “Start Debugging Driver” it tells me that I have an old version of “VBoxDD.dll” or “kdclient.dll” running, that can’t be i am using the newst version :'(
… I*ve tried to reinstall everything many times…didn’t work at all, always the same problem above =(thanxxx !!
hi guys,
I have the same problem :'(…my specs:
host: win7 x64 sp1
windbg: x86, 6.12…
visual studio 2010guest os: win7 x86
thank you very much =)
@OliT wrote:
Hi,
I have the problem that WinCDEmu is not working on my Windows 7 Ultimate (32-Bit). I had installed V3.1 one month ago and it worked perfectly. As I wanted to mount an ISO image yesterday it failed for unknown reasons (no new drive and no error indication). So I
- Uninstalled V 3.1, Rebooted[/*:11uu5u2p]
- Ran wcdcleanup, Rebooted[/*:11uu5u2p]
- Installed the latest V3.3.1, Rebooted[/*:11uu5u2p]
After this mounting an ISO image started the installation of a new device driver which timed out after 5 minutes with error 0x000005b4 which is just the error code for timeout (see the attached extract of setupapi.dev.log). One main difference of installed software on my system between the working state and the current state of failure is the installation of iTunes in the meantime which was already mentioned as a trouble maker in other threads.
Any ideas what might go wrong ?
>>> [Device Install (Hardware initiated) - BazisVirtualCDBusStandardDeviceVirtualCD_0000]
>>> Section start 2010/04/24 08:19:51.683
ump: Creating Install Process: DrvInst.exe 08:19:51.685
ndv: Retrieving device info...
ndv: Setting device parameters...
ndv: Searching Driver Store and Device Path...
dvi: {Build Driver List} 08:19:52.658
cpy: Policy is set to make all digital signatures equal.
dvi: Enumerating INFs from path list 'C:Windowsinf'
inf: Opened PNF: 'C:WindowsSystem32DriverStoreFileRepositorycdrom.inf_x86_neutral_db87d184bc84f910cdrom.inf' ([strings.0409])
dvi: Created Driver Node:
dvi: HardwareID - GenCdRom
dvi: InfName - C:WindowsSystem32DriverStoreFileRepositorycdrom.inf_x86_neutral_db87d184bc84f910cdrom.inf
dvi: DevDesc - CD-ROM Drive
dvi: DrvDesc - CD-ROM Drive
dvi: Provider - Microsoft
dvi: Mfg - (Standard CD-ROM drives)
dvi: ModelsSec - cdrom_device.NTx86
dvi: InstallSec - cdrom_install
dvi: ActualSec - cdrom_install
dvi: Rank - 0x00ff0000
dvi: Signer - Microsoft Windows
dvi: Signer Score - INBOX
dvi: DrvDate - 06/21/2006
dvi: Version - 6.1.7600.16385
dvi: {Build Driver List - exit(0x00000000)} 08:19:52.982
ndv: Selecting best match from Driver Store (including Device Path)...
dvi: {DIF_SELECTBESTCOMPATDRV} 08:19:52.985
dvi: Using exported function 'DvdClassInstaller' in module 'C:Windowssystem32storprop.dll'.
dvi: Class installer == storprop.dll,DvdClassInstaller
dvi: Using exported function 'StorageCoInstaller' in module 'C:Windowssystem32SysClass.Dll'.
dvi: CoInstaller 1 == SysClass.Dll,StorageCoInstaller
dvi: Using exported function 'CriticalDeviceCoInstaller' in module 'C:Windowssystem32SysClass.Dll'.
dvi: CoInstaller 2 == SysClass.Dll,CriticalDeviceCoInstaller
dvi: CoInstaller 1: Enter 08:19:53.013
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 08:19:53.016
dvi: CoInstaller 2: Exit
dvi: Class installer: Enter 08:19:53.019
dvi: Class installer: Exit
dvi: Default installer: Enter 08:19:53.022
dvi: {Select Best Driver}
dvi: Selected driver installs from section [cdrom_install] in 'c:windowssystem32driverstorefilerepositorycdrom.inf_x86_neutral_db87d184bc84f910cdrom.inf'.
dvi: {DIF_DESTROYPRIVATEDATA} 08:19:53.027
dvi: CoInstaller 1: Enter 08:19:53.029
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 08:19:53.032
dvi: CoInstaller 2: Exit
dvi: Class installer: Enter 08:19:53.035
dvi: Class installer: Exit
dvi: Default installer: Enter 08:19:53.038
dvi: Default installer: Exit
dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 08:19:53.041
dvi: Set selected driver complete.
dvi: Selected:
dvi: Description - [CD-ROM Drive]
dvi: InfFile - [c:windowssystem32driverstorefilerepositorycdrom.inf_x86_neutral_db87d184bc84f910cdrom.inf]
dvi: Section - [cdrom_install]
dvi: Signer - [Microsoft Windows]
dvi: Rank - [0x00ff0000]
dvi: {Select Best Driver - exit(0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 08:19:53.056
inf: {SetupCopyOEMInf: C:WindowsINFcdrom.inf} 08:19:53.057
inf: {SetupCopyOEMInf exit (0x00000050)} 08:19:53.059
inf: Opened PNF: 'C:WindowsSystem32DriverStoreFileRepositorycdrom.inf_x86_neutral_db87d184bc84f910cdrom.inf' ([strings.0409])
dvi: Selected driver installs from section [cdrom_install] in 'c:windowssystem32driverstorefilerepositorycdrom.inf_x86_neutral_db87d184bc84f910cdrom.inf'.
dvi: Set selected driver complete.
ndv: Driver selected, now performing install...
ndv: {Core Device Install} 08:19:53.068
inf: Opened INF: 'C:WindowsINFcdrom.inf' ([strings.0409])
inf: Saved PNF: 'C:WindowsINFcdrom.PNF' (Language = 0409)
inf: Opened PNF: 'C:WindowsINFcdrom.inf' ([strings.0409])
dvi: {DIF_ALLOW_INSTALL} 08:19:53.112
dvi: Using exported function 'DvdClassInstaller' in module 'C:Windowssystem32storprop.dll'.
dvi: Class installer == storprop.dll,DvdClassInstaller
dvi: Using exported function 'StorageCoInstaller' in module 'C:Windowssystem32SysClass.Dll'.
dvi: CoInstaller 1 == SysClass.Dll,StorageCoInstaller
dvi: Using exported function 'CriticalDeviceCoInstaller' in module 'C:Windowssystem32SysClass.Dll'.
dvi: CoInstaller 2 == SysClass.Dll,CriticalDeviceCoInstaller
dvi: CoInstaller 1: Enter 08:19:53.123
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 08:19:53.126
dvi: CoInstaller 2: Exit
dvi: Class installer: Enter 08:19:53.129
dvi: Class installer: Exit
dvi: Default installer: Enter 08:19:53.132
dvi: Default installer: Exit
dvi: {DIF_ALLOW_INSTALL - exit(0xe000020e)} 08:19:53.135
ndv: Installing files...
dvi: {DIF_INSTALLDEVICEFILES} 08:19:53.139
dvi: CoInstaller 1: Enter 08:19:53.140
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 08:19:53.143
dvi: CoInstaller 2: Exit
dvi: Class installer: Enter 08:19:53.146
dvi: Class installer: Exit
dvi: Default installer: Enter 08:19:53.149
dvi: {Install FILES}
inf: Opened PNF: 'c:windowssystem32driverstorefilerepositorycdrom.inf_x86_neutral_db87d184bc84f910cdrom.inf' ([strings.0409])
inf: {Install Inf Section [cdrom_install]}
inf: CopyFiles=cdrom_copyfiles (cdrom.inf line 92)
flq: CopyFiles from an inbox inf.
cpy: Open PnpLockdownPolicy: Err=2. This is OK. Use LockDownPolicyDefault
flq: QueueSingleCopy...
flq: Inf : 'c:windowssystem32driverstorefilerepositorycdrom.inf_x86_neutral_db87d184bc84f910cdrom.inf'
flq: SourceInf: 'c:windowssystem32driverstorefilerepositorycdrom.inf_x86_neutral_db87d184bc84f910cdrom.inf'
flq: SourceSection: [sourcedisksfiles]
flq: Source root path based on SourceInf
flq: SourceRootPath: 'C:WindowsSystem32DriverStoreFileRepositorycdrom.inf_x86_neutral_db87d184bc84f910'
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x09000000
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x09000000
flq: SourceRootPath - 'C:WindowsSystem32DriverStoreFileRepositorycdrom.inf_x86_neutral_db87d184bc84f910'
flq: SourceFilename - 'cdrom.sys'
flq: TargetDirectory- 'C:Windowssystem32DRIVERS'
flq: TargetFilename - 'cdrom.sys'
flq: SourceDesc - 'windows cd'
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {FILE_QUEUE_COPY exit(0x00000000)}
inf: {Install Inf Section [cdrom_install] exit (0x00000000)}
dvi: Processing co-installer registration section [cdrom_install.CoInstallers].
inf: {Install Inf Section [cdrom_install.CoInstallers]}
inf: {Install Inf Section [cdrom_install.CoInstallers] exit (0x00000000)}
dvi: Co-installers registered.
dvi: {Install INTERFACES}
dvi: Installing section [cdrom_install.Interfaces]
dvi: {Install INTERFACES exit 00000000}
dvi: {Install FILES exit (0x00000000)}
dvi: Default installer: Exit
dvi: {DIF_INSTALLDEVICEFILES - exit(0x00000000)} 08:19:53.199
ndv: Pruning file queue...
dvi: {_SCAN_FILE_QUEUE}
flq: ScanQ flags=620
flq: SPQ_SCAN_PRUNE_COPY_QUEUE
flq: SPQ_SCAN_FILE_COMPARISON
flq: SPQ_SCAN_ACTIVATE_DRP
flq: ScanQ number of copy nodes=1
flq: File 'C:Windowssystem32DRIVERScdrom.sys' pruned from copy.
sig: Using catalog 'C:Windowssystem32CatRoot{F750E6C3-38EE-11D1-85E5-00C04FC295EE}Microsoft-Windows-Common-Drivers-Package~31bf3856ad364e35~x86~~6.1.7600.16385.cat'.
cpy: DrpSetRegFileProt 'C:Windowssystem32DRIVERScdrom.sys' Status=0 Class=Inbox Windows protected
flq: ScanQ action=200 DoPruning=32
flq: ScanQ end Validity flags=620 CopyNodes=0
dvi: {_SCAN_FILE_QUEUE exit(0, 0x00000000)}
ndv: Committing file queue...
flq: {_commit_file_queue}
flq: CommitQ DelNodes=0 RenNodes=0 CopyNodes=0
flq: CommitQ early exit: No nodes are queued
flq: {_commit_file_queue exit OK}
ndv: Registering CoInstallers...
dvi: {DIF_REGISTER_COINSTALLERS} 08:19:53.285
dvi: CoInstaller 1: Enter 08:19:53.288
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 08:19:53.290
dvi: CoInstaller 2: Exit
dvi: Class installer: Enter 08:19:53.293
dvi: Class installer: Exit
dvi: Default installer: Enter 08:19:53.296
inf: Opened PNF: 'c:windowssystem32driverstorefilerepositorycdrom.inf_x86_neutral_db87d184bc84f910cdrom.inf' ([strings.0409])
inf: {Install Inf Section [cdrom_install.CoInstallers]}
inf: {Install Inf Section [cdrom_install.CoInstallers] exit (0x00000000)}
dvi: {DIF_DESTROYPRIVATEDATA} 08:19:53.304
dvi: CoInstaller 1: Enter 08:19:53.305
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 08:19:53.308
dvi: CoInstaller 2: Exit
dvi: Class installer: Enter 08:19:53.311
dvi: Class installer: Exit
dvi: Default installer: Enter 08:19:53.313
dvi: Default installer: Exit
dvi: {DIF_DESTROYPRIVATEDATA - exit(0xe000020e)} 08:19:53.316
dvi: Co-installers registered.
dvi: Default installer: Exit
dvi: {DIF_REGISTER_COINSTALLERS - exit(0x00000000)} 08:19:53.320
ndv: Installing interfaces...
dvi: {DIF_INSTALLINTERFACES} 08:19:53.323
dvi: Using exported function 'StorageCoInstaller' in module 'C:Windowssystem32SysClass.Dll'.
dvi: CoInstaller 1 == SysClass.Dll,StorageCoInstaller
dvi: Using exported function 'CriticalDeviceCoInstaller' in module 'C:Windowssystem32SysClass.Dll'.
dvi: CoInstaller 2 == SysClass.Dll,CriticalDeviceCoInstaller
dvi: CoInstaller 1: Enter 08:19:53.331
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 08:19:53.334
dvi: CoInstaller 2: Exit
dvi: Class installer: Enter 08:19:53.337
dvi: Class installer: Exit
dvi: Default installer: Enter 08:19:53.340
dvi: {Install INTERFACES}
inf: Opened PNF: 'c:windowssystem32driverstorefilerepositorycdrom.inf_x86_neutral_db87d184bc84f910cdrom.inf' ([strings.0409])
dvi: Installing section [cdrom_install.Interfaces]
dvi: {Install INTERFACES exit 00000000}
dvi: Default installer: Exit
dvi: {DIF_INSTALLINTERFACES - exit(0x00000000)} 08:19:53.349
ndv: Installing device...
dvi: {DIF_INSTALLDEVICE} 08:19:53.352
dvi: CoInstaller 1: Enter 08:19:53.353
dvi: CoInstaller 1: Exit
dvi: CoInstaller 2: Enter 08:19:53.358
dvi: CoInstaller 2: Exit
dvi: Class installer: Enter 08:19:53.361
dvi: Class installer: Exit
dvi: Default installer: Enter 08:19:53.364
dvi: {Install DEVICE}
inf: Opened PNF: 'c:windowssystem32driverstorefilerepositorycdrom.inf_x86_neutral_db87d184bc84f910cdrom.inf' ([strings.0409])
dvi: Processing Registry/Property directives...
inf: {Install Inf Section [cdrom_install]}
inf: {Install Inf Section [cdrom_install] exit (0x00000000)}
inf: {Install Inf Section [cdrom_install.Hw]}
inf: AddReg=nosync_addreg (cdrom.inf line 95)
inf: {Install Inf Section [cdrom_install.Hw] exit (0x00000000)}
dvi: {Writing Device Properties}
dvi: Provider name=Microsoft
dvi: DriverDate 06/21/2006
dvi: DriverVersion=6.1.7600.16385
dvi: Class name=CDROM
dvi: Manufacturer=(Standard CD-ROM drives)
dvi: Matching DeviceID=gencdrom
dvi: Strong Name=cdrom.inf:cdrom_device.NTx86:cdrom_install:6.1.7600.16385:gencdrom
dvi: {Writing Device Properties - Complete}
inf: {Install Inf Section [cdrom_install.Services]}
inf: AddService=cdrom,0x00000002,cdrom_ServiceInstallSection,cdrom_EventLog_InstallSection (cdrom.inf line 98)
inf: ServiceType=1 (cdrom.inf line 106)
inf: StartType=1 (cdrom.inf line 107)
inf: ErrorControl=1 (cdrom.inf line 108)
inf: ServiceBinary=C:Windowssystem32DRIVERScdrom.sys (cdrom.inf line 109)
inf: DisplayName="CD-ROM Driver" (cdrom.inf line 105)
inf: LoadOrderGroup="SCSI CDROM Class" (cdrom.inf line 110)
dvi: Add Service: Modified existing service 'cdrom'.
inf: AddReg=autorun_addreg (cdrom.inf line 111)
inf: AddReg=cdrom_EventLog_AddReg (cdrom.inf line 114)
inf: {Install Inf Section [cdrom_install.Services] exit(0x00000000)}
dvi: Updated reflected section names for: cdrom.inf
dvi: {Install DEVICE exit (0x00000000)}
dvi: Writing common driver property settings.
dvi: DriverDescription=CD-ROM Drive
dvi: DeviceDisplayName=CD-ROM Drive
dvi: Install Device: Restarting device. 08:19:53.947
ump: Server install process exited with code 0x000005b4 08:24:53.354
<<< Section end 2010/04/24 08:24:53.356
<<< [Exit status: FAILURE(0x000005b4)]
Hey i heard creating a driver to make a mountable “Burner” is alot of work, but how much work would this method i describe now be? (sorry it might not be explained clearly)
As i can see you can now Save a mounted iso to a Image, great.
What if you “fake” your Driver to be burner, so when you move files onto it windows will “temporary” Save it on the disc (though obviously its not wrtting anything yet).
So now you would try to Burn but it will fail, cause the “fake” doesnt really work to “Burn” with the internal thing.
But what if we would now read the buffer for the files instead, so we can use our own Write Iso function instead.Would this be way to complicated to implement? As this sort of function would make a tool like UltraISO obsolute for simple editing of your iso, as you can simply mount it, edit it, and Save it back as iso.
