Jump to content

GSB

Member
  • Posts

    3
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Everything posted by GSB

  1. Tip - From what I read, an RPC2 DVD drive will need a DVD of the region that is being set, to be in the drive, at the time of setting the region. From what I have read, I belive "storprop.dll" could be the answer, but I have no idea what function(s) I need This out of my area and league to be honest. Does this give anyone any ideas? thanks
  2. Hi, Firstly, I hope this is the correct section to ask. The background: I have repackaged a DVD player application (into an MSI). However, as this is deployed to workstation's where the users are not Admins, I have a problem on workstations where the DVD drive does not yet have it's region set (preferably to 2!). When run as an admin user, the application prompts on first use in this scenario, for the region to be set - like setting the region in device manager I guess. This I believe sets the region on the DVD drive firmware. However, as a regular user, this fails. WIthout a region set to something on the drive, the software fails. So, I am looking for a way to script or automate setting the region code of DVD drives where it is not already set - perhaps by a script, DLL or api call. I will probably implement this via a custom action in my MSI which will have elvated privileges. I should mention the OS is Windows XP Pro. Any one got any ideas on programatically setting DVD region (only from a not set state, I am not trying to hack anything)? Any help greatly appreciated. Graham
  3. Hi guys. This is great! I have previously lurked on here and indeed read the document about the PNP drivers paths/ordering the other day prior to this thread starting. I then questioned in my mind whether it was valid or not, so am very happy this thread has started, to the extend I finally signed up!!! Back on topic: 1. Yes, you can use subfolders, but they need to be specified in you unattend file individually. At least we have some choice over folder design since the old W2k pre SP2 96 character limit for the PNP drivers path! However, I don't understand your logic of having the top level folders numbered. Number ing Subfolders makes sence ie Video\000_Trident Video\0001_Trident In this example if you NEED to include two varying Trident Video drivers for some sort of compatability issue, you know the newer driver you place in the 000 folder will be seen 1st. However, how does numbering the top level folders help, apart from perhaps a very negligable performance increse? The model below is what I mean 000=smbus/chipset 001=lan 002=usb/firewire/serial i-o 003=audio 004=video Surely Windows only even looks for a driver, if it finds a device in the first place?? The example I am questioning seems to infer Windows looks at what drivers it has and then looks to see if it has some hardware to match it?! Surley it wouldn't matter if you had at the top level: 000_Sound 009_Chipset If Windows finds chipset hardware 1st it will still go looking for a chipset driver, in whatever paths you have chosen. Sure it will look in 000_Sound first, as it routes through folders in alphabetical sequence, but it doesn't mean it will install the Sound drivers first just as they are in the first folder does it??? Likewise a chipset driver would not definately install 1st just as it was in a 000_chipset folder? To me, the folders should be designed logically, but have no actaul impact on the older devices are detected or installed. What do you think? Graham
×
×
  • Create New...