VS-100 and windows 8

As the vs-100 has been out a long time, when / will there be a windows 8 driver available? or is this not going to be supported in the future? I only got this unit a few months ago, it would be a shame to not be able to use it in windows 8, and i dont want to upgrade to windows 8 until there is a driver for my interface.

Cheers
Bassman

Since the V-Studios 700 and 100 have always had the same drivers and since the 700 will almost certainly be W8 compatible, I'm guessing that the 100 will continue to follow suit. Just an assumption though.

Roland is working on Win 8 drivers right now. As they did with XP, Vista, and 7, they will release drivers for 8 when the OS is officially released to the public via retail channels (October is what I last heard). Until then they will continue to test and refine the Win 8 drivers.

HTH.

SP

Looking forward to that! I just tweaked the inf file on the drivers so it runs in Windows 8 and Windows 8 is soooo much more stable and efficient with audio. I can put the Asio buffer to the lowest setting possible and it is rock solid. I never got anywhere near that on Windows 7!

Thanks Seth.  I have been running the Windows 8 released to manufacturing version for a couple months.  I suppose the great news is that Sonar X1 Producer Expanded installed and works fine but not being able to use the vs-100 is quite an inconvenience and we are weeks away from general availability.  Today I just got my access to Sonar X2 and really want to use it with the v-100
 
I am more than happy to beta test the new drivers in whatever state they are currently in.
 
 

Good thing I have a dual boot win7/win8 system. The changes to the inf don't work on my x64 install. The new win8 hyper-v is nice, akthough I'm not too sure how Sonar works in a virtual machine ;-)

Hi guys,

Can we hear when we may expect a driver? Win 8 is now out, and though the ms upgrade advisor says nothing about it, it doesn't recognize the VS-100 after the upgrade.

Thank you!

Phave


Hi guys,

Can we hear when we may expect a driver? Win 8 is now out, and though the ms upgrade advisor says nothing about it, it doesn't recognize the VS-100 after the upgrade.

Thank you!

 
 
Sonar v-Studio not working with Sonar on Windows 8 is disappointing with not even a beta driver available on the site.
 
I tried installing the Win 7 driver using compatibility mode, that did not work either.

Timo Finkbeiner


Hello Cakewalk / Roland,

do you have some news? When will be a driver for Windows 8 released?
I also want to install Windows 8, but I have to wait until my VS-100 will work fine.

Kind regards,
T. Finkbeiner

Ditto - waiting to upgrade for the news that Roland has released drivers for my V-Studio 100.  Hoping to hear something official soon.

Finally got it working!

I kept getting the error that the OS was not compatible even though I edited the inf properly.

Used the compatibility trouble shooter (right click on setup.exe for the option)

Selected that it worked before using Windows 7, and it guided me through uninstalling the driver and rebooted to complete the uninstall.

I rebooted again to select not using signed drivers, and then was able to install the modified driver.

Working great so far.

Hi,
hope the driver will be ready soon.
Even older products from Roland/Edirol like the M-16DX already have Windows 8 - Drivers, and the MIDI-Controller-Keyboards like the A800 Pro too.

So come on please.

T. Finkbeiner

Hi,
now I saw this banner on the top of the homepage with the announcement of new drivers for Roland hardware. But no Drivers for the VS-100 yet. But drivers for older hardware, like the PCR-M1, which I soled a few weeks ago (now I have a A-Pro 800 with W8 drivers). This keyboard controller is quite older than the VS-100, so I hope the VS-100 will be the next in the line.

Timo Finkbeiner

Yeah, I think it's probably time to get the driver out... The UA-101 had a driver day one, I think, so, you know, what's the hold up? 

I really hope this isn't going the route of stopping support on the VS-100. Given users are able to make the drivers work with modifications to BS driver signing code within the driver makes me think that could be what's happening, as that isn't a hard thing to modify in creating a new Windows 8 driver.
Of course, I can't and don't know; maybe Roland is working on making the drivers better or something? Maybe it's in QA? Dunno. Regardless, surprised it wasn't part of day one W8 drivers. Does the VS-100 have a lower priority because it's related to Cakewalk rather than being a straight Roland product? I'll quit ranting and go back to using my Axe FX II drivers, as they work great without any modifications after updating to Windows 8...   

Don't drop in here often enough, sorry to not get back quickly, here's the 32bit inf: find it by going; files-win7-files-32bit-files this for the 32bit version 64 bit go to 64bit-files and apart from the 64bit detail all inf changes are the same ; Installation inf for the VS-100 ; ; Copyright (c) 2011 Roland Corporation ; [Version] Signature="$Windows NT$" Class=MEDIA ClassGUID={4d36e96c-e325-11ce-bfc1-08002be10318} Provider=%MfgName% DriverVer=10/26/2011,2.00.01.0000 ;---------------------------------------------------------------; [DestinationDirs] RDID0099.Files.Asio = 11 RDID0099.Files.User = 11 RDID0099.Files.Inst = 11 RDID0099.Files.Ext = 10,system32\drivers ; %SystemRoot%\system32\drivers DefaultDestDir = 10,system32\drivers ; %SystemRoot%\system32\drivers [SourceDisksNames] 1=%RDID0099DiskName%,, [SourceDiskSFiles] RDWM1099.SYS=1 RDAS1099.DLL=1 RDDP1099.DAT=1 RDCP1099.CPL=1 RDCI1099.DLL=1 ;---------------------------------------------------------------; [Manufacturer] %MfgName%=Roland,NTx86.6.1,NTx86.6.2 ;[ControlFlags] ;ExcludeFromSelect=* [Roland] ;; WindowsVista or WindowsXP or Windows2000 or Windows9X / ME ;; not supported [Roland.NTx86.6.1] ;; Windows7 %RDID0099DeviceDesc%=RDID0099Install, USB\VID_0582&PID_00EB ; VS-100 [Roland.NTx86.6.2] ;; Windows8 %RDID0099DeviceDesc%=RDID0099Install, USB\VID_0582&PID_00EB ; VS-100 ;===============================================================; [RDID0099Install] Include=ks.inf,wdmaudio.inf Needs=KS.Registration,WDMAUDIO.Registration CopyFiles=RDID0099.Files.User,RDID0099.Files.Ext,RDID0099.Files.Asio AddReg=RDID0099AddReg [RDID0099Install.CoInstallers] AddReg=RDID0099CoInstallers.AddReg CopyFiles=RDID0099.Files.Inst [RDID0099CoInstallers.AddReg] HKR,,CoInstallers32,%REG_MSZ%,"RdCi1099.dll,ProcCoInst" [RDID0099AddReg] HKR,,DevLoader,,"*ntkern" HKR,,AssociatedFilters,,"wdmaud,swmidi,redbook" HKR,,Driver,,rdwm1099.sys HKR,,NTMPDriver,,"rdwm1099.sys" HKR,Drivers,SubClasses,,"wave,midi,mixer" HKR,Drivers\wave\wdmaud.drv,Driver,,wdmaud.drv HKR,Drivers\midi\wdmaud.drv,Driver,,wdmaud.drv HKR,Drivers\mixer\wdmaud.drv,Driver,,wdmaud.drv HKR,Drivers\wave\wdmaud.drv,Description,,%RDID0099DeviceDesc% HKR,Drivers\midi\wdmaud.drv, Description,,%RDID0099DeviceDesc% HKR,Drivers\mixer\wdmaud.drv,Description,,%RDID0099DeviceDesc% HKLM,%MediaCategories%\%WDM.Tp11.szPname.GUID%,Name,,%WDM.Tp11.szPname% HKLM,%MediaCategories%\%WDM.Tp11.szPname.GUID%,Display,1,00,00,00,00 HKLM,%MediaCategories%\%WDM.Tp12.szPname.GUID%,Name,,%WDM.Tp12.szPname% HKLM,%MediaCategories%\%WDM.Tp12.szPname.GUID%,Display,1,00,00,00,00 HKLM,%MediaCategories%\%WDM.Tp13.szPname.GUID%,Name,,%WDM.Tp13.szPname% HKLM,%MediaCategories%\%WDM.Tp13.szPname.GUID%,Display,1,00,00,00,00 HKLM,%MediaCategories%\%WDM.Tp14.szPname.GUID%,Name,,%WDM.Tp14.szPname% HKLM,%MediaCategories%\%WDM.Tp14.szPname.GUID%,Display,1,00,00,00,00 HKLM,%MediaCategories%\%WDM.Tp15.szPname.GUID%,Name,,%WDM.Tp15.szPname% HKLM,%MediaCategories%\%WDM.Tp15.szPname.GUID%,Display,1,00,00,00,00 HKLM,%MediaCategories%\%WDM.Tp16.szPname.GUID%,Name,,%WDM.Tp16.szPname% HKLM,%MediaCategories%\%WDM.Tp16.szPname.GUID%,Display,1,00,00,00,00 HKLM,%MediaCategories%\%WDM.Tp17.szPname.GUID%,Name,,%WDM.Tp17.szPname% HKLM,%MediaCategories%\%WDM.Tp17.szPname.GUID%,Display,1,00,00,00,00 HKLM,%MediaCategories%\%WDM.Tp18.szPname.GUID%,Name,,%WDM.Tp18.szPname% HKLM,%MediaCategories%\%WDM.Tp18.szPname.GUID%,Display,1,00,00,00,00 [RDID0099Install.Services] AddService = RDID1099, 0x00000002, RDID0099_Service_Inst [RDID0099_Service_Inst] DisplayName = %RDID0099DeviceDesc% ServiceType = 1 ; SERVICE_KERNEL_DRIVER StartType = 3 ; SERVICE_DEMAND_START ErrorControl = 1 ; SERVICE_ERROR_NORMAL ServiceBinary = %10%\system32\Drivers\rdwm1099.sys ;;; ;; [RDID0099.Files.Ext] Rdwm1099.sys [RDID0099.Files.User] RDCP1099.CPL RDDP1099.DAT [RDID0099.Files.Inst] RdCi1099.dll [RDID0099.Files.Asio] rdas1099.dll [RDID0099Install.Interfaces] AddInterface=%KSCATEGORY_AUDIO%, %KSNAME_Wv11%, WDM.Interface.Wv11 AddInterface=%KSCATEGORY_RENDER%, %KSNAME_Wv11%, WDM.Interface.Wv11 AddInterface=%KSCATEGORY_CAPTURE%, %KSNAME_Wv11%, WDM.Interface.Wv11 AddInterface=%KSCATEGORY_AUDIO%, %KSNAME_Wv12%, WDM.Interface.Wv12 AddInterface=%KSCATEGORY_RENDER%, %KSNAME_Wv12%, WDM.Interface.Wv12 AddInterface=%KSCATEGORY_CAPTURE%, %KSNAME_Wv12%, WDM.Interface.Wv12 AddInterface=%KSCATEGORY_AUDIO%, %KSNAME_Wv13%, WDM.Interface.Wv13 AddInterface=%KSCATEGORY_RENDER%, %KSNAME_Wv13%, WDM.Interface.Wv13 AddInterface=%KSCATEGORY_CAPTURE%, %KSNAME_Wv13%, WDM.Interface.Wv13 AddInterface=%KSCATEGORY_AUDIO%, %KSNAME_Wv14%, WDM.Interface.Wv14 AddInterface=%KSCATEGORY_RENDER%, %KSNAME_Wv14%, WDM.Interface.Wv14 AddInterface=%KSCATEGORY_CAPTURE%, %KSNAME_Wv14%, WDM.Interface.Wv14 AddInterface=%KSCATEGORY_AUDIO%, %KSNAME_Wv15%, WDM.Interface.Wv15 AddInterface=%KSCATEGORY_RENDER%, %KSNAME_Wv15%, WDM.Interface.Wv15 AddInterface=%KSCATEGORY_CAPTURE%, %KSNAME_Wv15%, WDM.Interface.Wv15 AddInterface=%KSCATEGORY_AUDIO%, %KSNAME_Md11%, WDM.Interface.Md11 AddInterface=%KSCATEGORY_RENDER%, %KSNAME_Md11%, WDM.Interface.Md11 AddInterface=%KSCATEGORY_CAPTURE%, %KSNAME_Md11%, WDM.Interface.Md11 AddInterface=%KSCATEGORY_AUDIO%, %KSNAME_Md12%, WDM.Interface.Md12 AddInterface=%KSCATEGORY_RENDER%, %KSNAME_Md12%, WDM.Interface.Md12 AddInterface=%KSCATEGORY_CAPTURE%, %KSNAME_Md12%, WDM.Interface.Md12 AddInterface=%KSCATEGORY_AUDIO%, %KSNAME_Topology%, WDM.Interface.Topology [WDM.Interface.Wv11] AddReg=WDM.Interface.Wv11.AddReg [WDM.Interface.Wv11.AddReg] HKR,,CLSID,,%Proxy.CLSID% HKR,,FriendlyName,,%WDM.Wv11.szPname% [WDM.Interface.Wv12] AddReg=WDM.Interface.Wv12.AddReg [WDM.Interface.Wv12.AddReg] HKR,,CLSID,,%Proxy.CLSID% HKR,,FriendlyName,,%WDM.Wv12.szPname% [WDM.Interface.Wv13] AddReg=WDM.Interface.Wv13.AddReg [WDM.Interface.Wv13.AddReg] HKR,,CLSID,,%Proxy.CLSID% HKR,,FriendlyName,,%WDM.Wv13.szPname% [WDM.Interface.Wv14] AddReg=WDM.Interface.Wv14.AddReg [WDM.Interface.Wv14.AddReg] HKR,,CLSID,,%Proxy.CLSID% HKR,,FriendlyName,,%WDM.Wv14.szPname% [WDM.Interface.Wv15] AddReg=WDM.Interface.Wv15.AddReg [WDM.Interface.Wv15.AddReg] HKR,,CLSID,,%Proxy.CLSID% HKR,,FriendlyName,,%WDM.Wv15.szPname% [WDM.Interface.Md11] AddReg=WDM.Interface.Md11.AddReg [WDM.Interface.Md11.AddReg] HKR,,CLSID,,%Proxy.CLSID% HKR,,FriendlyName,,%WDM.Md11.szPname% [WDM.Interface.Md12] AddReg=WDM.Interface.Md12.AddReg [WDM.Interface.Md12.AddReg] HKR,,CLSID,,%Proxy.CLSID% HKR,,FriendlyName,,%WDM.Md12.szPname% [WDM.Interface.Topology] AddReg=WDM.Interface.Topo.AddReg ;; warning!! must be "Topo" because "Topology" is too long [WDM.Interface.Topo.AddReg] HKR,,CLSID,,%Proxy.CLSID% HKR,,FriendlyName,,%WDM.Topology.szPname% ;---------------------------------------------------------------; [Strings] MfgName="Roland" RDID0099DiskName="VS-100 Driver Installation disk" RDID0099DeviceDesc="VS-100" Proxy.CLSID="{17CCA71B-ECD7-11D0-B908-00A0C9223196}" KSCATEGORY_AUDIO="{6994AD04-93EF-11D0-A3CC-00A0C9223196}" KSCATEGORY_RENDER="{65E8773E-8F56-11D0-A3B9-00A0C9223196}" KSCATEGORY_CAPTURE="{65E8773D-8F56-11D0-A3B9-00A0C9223196}" KSNAME_Wv11="Wave1-1" KSNAME_Wv12="Wave1-2" KSNAME_Wv13="Wave1-3" KSNAME_Wv14="WaveIn1-1" KSNAME_Wv15="WaveIn1-2" WDM.Wv11.szPname="1-2 (VS-100)" WDM.Wv12.szPname="3-4 (VS-100)" WDM.Wv13.szPname="5-6 (VS-100)" WDM.Wv14.szPname="DIGITAL (VS-100)" WDM.Wv15.szPname="MAIN (VS-100)" KSNAME_Md11="Midi1-1" KSNAME_Md12="Midi1-2" WDM.Md11.szPname="MIDI (VS-100)" WDM.Md12.szPname="CONTROL (VS-100)" KSNAME_Topology="Topology" WDM.Topology.szPname="VS-100 Mixer" MediaCategories="SYSTEM\CurrentControlSet\Control\MediaCategories" WDM.Tp11.szPname="1-2" WDM.Tp12.szPname="3-4" WDM.Tp13.szPname="5-6" WDM.Tp14.szPname="1-2" WDM.Tp15.szPname="3-4" WDM.Tp16.szPname="5-6" WDM.Tp17.szPname="DIGITAL" WDM.Tp18.szPname="MAIN" WDM.Tp11.szPname.GUID = "{C461D13F-4EDF-45d6-A396-F031F80A3A72}" WDM.Tp12.szPname.GUID = "{1CC2331E-767E-446d-AC6F-22630DC8D3A8}" WDM.Tp13.szPname.GUID = "{C8606FCD-C00E-4bb2-A4E9-9A8DD23F61BD}" WDM.Tp14.szPname.GUID = "{C114181C-362F-4305-801E-445D5048C137}" WDM.Tp15.szPname.GUID = "{4817EAC3-B69D-45b5-8D0A-E4B88371457F}" WDM.Tp16.szPname.GUID = "{CEDC8687-1889-40c2-B151-A1C4B4856773}" WDM.Tp17.szPname.GUID = "{674ED650-0A59-418e-86AF-A394E3D03642}" WDM.Tp18.szPname.GUID = "{3458CA25-35A4-4501-8A18-5D40F0B2B395}" REG_MSZ = 0x00010000 then to bypass driver signing (only neede when installing not every time) 1. Open start screen then open charms by pointing to the upper right corner with mouse 2. Select Settings (right bar)/More PC Settings (at bottom) 3. Then go General/Advanced Startup/Restart Now/Troubleshoot/Advanced Options/Windows Startup Settings/Restart 4. After reboot from displayed options select 7th which temporally removes requirement for drivers to be signed 5. Windows starts, point to device manager by right clicking on the lower left corner of desktop or start screen 6. Select GR-55 from unknown devices 7. Right click->Update driver->manual 8. Direct to the folder with the modified .inf file from point 1. 9. Agree to install unsigned driver in the warning dialog done!

Yikes. Not looking great on the V-Studio driver front... Here's a response from Roland US:

From Roland Support (US): We have sent a request for Windows 8 drivers to our corporate Roland, BOSS and Cakewalk headquarters in Japan. At this time, we do not have any information regarding when they plan to release them. Sincerely, Roland Product Support


I'll let you know if I hear anything else.