call me retarded but...
Home > Home Recording Forum > Computers & Software > call me retarded but...
Posted on Feb 27, 2013 04:51 pm
truthnaction
Member Since: May 21, 2010
i went from the Tascam us-800 to the us-1800. I did this because the x64 drivers didn't work on the 800, and Ive read the success of all that for the 1800.... but I failed to realize I shoulda looked into the success of people running it on windows 8.
I have an acer aspire v5-551, 4gb ram, amd a8.
I tried a few ways, but my hunch is that from doing all of them, ive come across the correct way and it failed because of (MAYBE) bad uninstalls? they all said they were successful, but maybe I should open regedit and find all the tscam related stuff and try again? I just don't want to do this every time I try a reinstall. I got this today and its really bothering me. ive found 1 post on amazon were someone had success with a x64 win8. he doesn't specify the chipset, but from what I read in the manual, it shows amd Athlon as one of the minimum requirements, so that shouldn't be the case.
anyone wanna help me google? anyone had this issue? please don't anyone rant on how I should buy something else, or shoulda gotten something else. im not. I know this can work. there is a way. ill even dual install 7 if I relly have to, but I REALLY don't want to. that's last resort.
[ Back to Top ]
Dematrixhttp://www.reverbnation.com/2ndgMember
Since: Nov 27, 2007
Feb 27, 2013 06:14 pm dude its funny, well not so, but i also had an aspire years ago, probably not the same model but man, i went thru hell trying to figure out why it wouldnt work with a lexicon omega. end of the day the lexicon was a heap o poo and the laptop was just as bad, everytime i plugged into the lapy it would blue screen and then i would have to re install all sorts of things like my drivers for cd drive amongst many others.
not sure if these issues are related to yours or not but if you want my advice try installing all ya stuff on another computer and see if you have better luck just for arguements sake ya know?
end of the day i got a full refund from where i bought the computer because its couldnt do the job of plug n play (technically) and it was a total POS. im real sus on anything Acer. Not that ya wanna hear that right now.
HippieRockstar Vatican AssassinMember
Since: Mar 20, 2009
Feb 28, 2013 02:26 pm I have no idea if this would do the trick... but try changing the compatibility modes to all the associated EXE's to Windows 7 mode (highlight the EXE, select properties, compatibility).
According to their website, it doesn't show Windows 8 being supported. But 8 is just 7 with Metro, so the skeleton is pretty much the same. Maybe just needs a little extra help. There's also x64 drivers out there... which I'm assuming you grabbed. I think you can force those to install, even if meant for Windows 7.
tascam.com/product/us-1800/downloads/
Sort of a pain in the ***, but you could also run SysInternals Process Monitor to record what registry keys are being 'set value, write value' during an install. This way, you know what hives to hit on cleanup if an uninstall isn't very clean.
Mar 03, 2013 02:16 pm yeah ive actually gone into the registry and I couldn't find a single us1800 entry... but I did find us800 ones (this is after uninstalling both). after I deleted those (in hopes maybe the 800 gave an issue to the 1800... not the case). tried reinstalling, nothing. did compatibility on the setup file, nothing. did compatibility with everything possible in the driver, and I got the control panel (for the Tascam), but it still had said it wasn't installed properly... and sonar didn't see it. I booted in advanced mode with driver signing turned off... and from the beginning I already made sure to change the properties of the setup file to always run in administrator mode. I had a feeling it wasn't gonna be a smooth ride. im a total geek. ive been deep into computers since 95. my dads 25+ year experienced software engineer and nearing 10 year computer security, so don't anyone hold back from suggesting doing something scary! we know what were doing!
im not getting blue screens. the only blue screen I got was with the us-800 because the x64 driver has a memory leak. its the only blue screen ive ever gotten on 8, and I knew i was gonna force it to happen (just wanted to test y not?). that's y I got the 1800, is cuz the x64 driver DOES work. I ran it on my sisters win7 x64 laptop and my dads win7 x64 tower. if I have to, ill dual boot, but in order to do that, I have to uninstall 8 then load 7 then 8 (well windows always needed to be installed in chronological order, but idk maybe they did something crazy with the way the boot manager in 8. idk. ill check it out).
windows 8 is not 7 with metro. its got the same feel (on the desktop) and very similar look to it, but its not the same. the os was rewritten from the ground up. it just depends on ur way of lookin at it. I mean, 7 could "be" xp as far as looks if u change the images that make up the graphical interface.
Dematrixhttp://www.reverbnation.com/2ndgMember
Since: Nov 27, 2007
Mar 03, 2013 10:40 pm just sounds very much like the issues i had with an acer lapy, is it a new lapy? can get refund on it?
Mar 05, 2013 02:43 am it is. but I don't think it has much to do with the brand name. its an AMD chipset. the win7 machine I tried had the same chipset. the tower is intel. it works on both. its gotta be something that 8 is doing weird. if I install 7 on here too, im not going to get the random programs that the computer came with, by acer. itll just be an amd chipset with plain win7... and I know thatll work.... well not tested of course, but I know it will. but I have a hunch its not any weird acer product that's toyin with me. its just 8 being as funky as it is.
Im looking into all kinds of weird ways that 8 can boot. theres so many random security measures I never heard of.
HippieRockstar Vatican AssassinMember
Since: Mar 20, 2009
Mar 05, 2013 09:21 am Quote:
windows 8 is not 7 with metro. its got the same feel (on the desktop) and very similar look to it, but its not the same. the os was rewritten from the ground up
Straight from the horses mouth.... just sayn!! LOL!!
It's Windows reimagined built upon the solid foundation of Windows 7 Enterprise speed and reliability. Windows 8 Enterprise delivers the power and familiarity you want, along with new ways for people to interact with line of business apps, and support for new Windows 8 devices.
www.microsoft.com/en-us/w...8/default.aspx.
Reimagined is not the same as Rebuilt. From my perspective (in a corporate environment), Group policy, reg keys, file paths, control panel, administrative tasks, domain joins, RSAT, UAC, Folder Redirection, IE Security, Sync Center..... all the same as Windows 7. The only difference to how I manage both OSs is use the 'Windows' key more on my keyboard to toggle between 7 mode and Metro mode.
That said.... it would seem very reasonable to have the Windows 7 drivers for your device working. Keep trying....it'll show up on Google eventually!!!
Mar 06, 2013 04:18 pm i stand corrected :P lol
however, the windows 7 driver still doesn't work. ive read something about legacy drivers for firewire not being in 8 and are in 7... people have manually moved the drivers and installed them to their 8 machine and everything ran smooth for them afterwards [installing their firewire device]. im wondering if this is a similar issue. I cant find anything about that though.
Mar 06, 2013 11:52 pm [SOLVED] THIS COULD BE HELPFUL FOR FUTURE WINDOWS 8 OWNERS USING USB INTERFACE!!!!
i booted in advanced mode, started with driver signing disabled, from there, loaded cmd in administrator and typed in the command:
bcdedit /set loadoptions DISABLE_INTEGRITY_CHECKS
made sure ALL executables were in windows 7 compatibility and set to administrator.... install went smooth. rebooted back into normal mode and no problems! everything works great! if u re-enable this code, it wont work again. good by windows security feature that i never cared for t begin with... i know what im installing.
Mar 07, 2013 07:08 am Awesome, glad you found the issue. Not too surprising of a fix now that you mention it, never thought about that silly administrator setting issue...I've had that issue before with other miscellaneous computer problems.
Good find. Congrats.
