Instructions and drivers for Vista on the Samsung Q1
Last week I found myself in a bit of a dilemma with my Samsung Q1P; after wiping it clean, I couldn’t find the drivers and specific order of installation. Previously I had referred to a great listing at psybertech.net but the pages I had bookmarked were no longer there. I was able to get the order of installation through Google’s cache of the page and eventually ended up at the Samsung UK support site to get the files I needed. Sounds convoluted, but it worked. Even better: you don’t have to follow my process to get the process!While looking for what I needed in a panic, I reached out to fellow Tablet MVP, Frank Garcia (aka: Ctitanic). Frank kindly offered to host the ordered instructions along with links to the Samsung files. The list is right here for your viewing pleasure! Thanks a ton, Frank!
I just did this myself last week. Actually, it isn’t that difficult. You can install everything in any order (or at least alphabetically) and it will work. The hardest part is the digitizer, because those drivers aren’t available from Samsung. You can read more about it (and download the drivers) from here: http://ultramobilepc-tips.blogspot.com/2007/04/finally-hid-support-for-all-q1s-with.html Best of all, you don’t need to use the VB script that way.
Right now I’m trying to make the 915 drivers look like 945 so I can enable Aero, but everything works sparkling as is, so I’m not rocking the boat to hard. It’s quite possibly as close to a preloaded machine as you can get. Worst case scenario, if you get something wrong, just use the system restore to a point before you installed that rogue driver.
It’s always a pleasure to help!
Hey Ryan, keep us posted of any progress.
I need these so I can reformat the HDD on my original Q1 and install Vista Ultimate all fresh and shiny…
Woadan
I still have this bookmarked:
http://origamiproject.com/forums/thread/16987.aspx
It’s most likely outdated.
I just remember the order is important for installing the menu ui, display manager, and magic keyboard.
What’s missing from that is Frank’s HID driver for the touchscreen.
Other apps that should be installed are the floattip and UMPCscrollbar.
I did notice on one of the Samsung driver sites (maybe the UK?) that there’s a new firmware for bluetooth and drivers.
Samsung has a good page with everything. At least my q1 (not q1p) uses them and runs vista just fine.
http://www.samsung.com/us/support/search/supportSearchResultView.do?group=&group_cd=&type=&type_cd=&subtype=&subtype_cd=&model_nm=&dType=D&vType=L&mType=&model_cd=&menu=download&prd_ia_cd=&acc_ia_fl=&disp_nm=Q1P+Vista
note that you need to go down and hit the tab for driver or software.
I will. Currently everything is working right now, so I don’t feel like messing with it again right now. I was able to install the 945 driver, but was unable to get the 910/915 hardware to use it, I kept coming up in VGA Safe mode. I’m not really surprised, but I had read instances where early RC1 drivers were installed like that. I also wouldn’t expect there to be significant hardware difference between the two chipsets. I still feel like it a should be possible, but clearly it will still take some more work.
I did a lot more reading over the weekend.
There’s a third-party driver in the works, but nothing coming out of Intel. In builds of Vista, post Beta 2, you need WDDM drivers. the drivers that allowed for Aero on Beta 2 were not WDDM and will not work at all with the final build of Vista. I did some more research, and while I believe a WDDM driver could be written for the 915 chipset, I wouldn’t count on that coming from Intel. It may be possible to write a middle layer driver which provides a WDDM interface to the official Intel drivers, but I’m nor sure the results would be any better. I suspect movie maker doesn’t run because the Windows Experience Index (WEI) is too low, (pegged at 1.0 because of missing DX drivers). It may be possible to provide overriding scores as a way to bypass that requirement. Offhand, I suspect there may be a way to observe what WinSAT writes to and calls, and then tweak those calls with something more to our liking. This would of course be 100% unofficial.
we wouldn’t get AERO with this fix, but maybe we can restore some functionality that we shouldn’t be missing.