Long driver pack na...
 
Notifications
Clear all

We appreciate the contributions many of you have been able to make towards repairing the storm damage and keeping a roof over our heads. With your help we’ve been able to complete much of the critical work. There is still work to be done to secure the house and your continued support will be a huge help.

Guests have read-only access to our forums. If you wish to participate you will need to register. Be sure to activate your account from the email sent to you when you register.

Long driver pack name

9 Posts
2 Users
0 Reactions
166 Views
(@francisw)
Active Member Registered
Joined: 8 months ago
Posts: 7
Topic starter  

Hi Glenn (all). I originally posted a query about this months ago ( https://www.glenn.delahoy.com/community/snappy-driver-installer-origin/long-driver-pack-name/#post-4015) & then failed to follow up when you requested a screenshot. I'm unable to comment or post the screenshot in that thread that now as I think you closed it due to inactivity.

From that original post "it's very helpful to look at why a particular driver is being recommended over the currently installed one.
SDIO should allow that, the dialogue/overlay that pops up when you leave the cursor on a driver gives details of the recommended new/better/whatever driver over the current in the bottom left & bottom right "panes".
However, for most of what I'm trying to look at, the right panes aren't visible, because the top left pane contains the driver pack name & this is so long (Eastern - Chinese? - characters) that this pushes the right of the dialogue off the screen"

Below is the screenshot requested (taken yesterday, from current version). I've now noticed the option around "Show driver pack names", which can remove the very long names from the main interface. If this carried through to the modal that pops up on hover that would sort this (that or text wrapping or limiting on the pack name).


   
Quote
Glenn
(@glenn)
Member Admin
Joined: 8 years ago
Posts: 1926
 

I have no idea why that looks like that. I would expect to see the driver pack file name exactly how it was created: DP_XXX_yymmw.7z

 


   
ReplyQuote
(@francisw)
Active Member Registered
Joined: 8 months ago
Posts: 7
Topic starter  

So these very long strings of Eastern (Chinese?) characters are unexpected?  I tried to screenshot one & use image search to translate, but couldn't due to low res/high aspect ratio.

As mentioned previously I've had this across several versions of SDIO & on 2 different Windows installs.

This post was modified 3 weeks ago by FrancisW

   
ReplyQuote
(@francisw)
Active Member Registered
Joined: 8 months ago
Posts: 7
Topic starter  

The screenshot is from my left, of 2, monitors & in some cases the pack name is so long it pushes the 2 right hand panes even off the right hand edge of the right hand screen. In other cases (so the driver pack name isn't the same in each case) I manage to get the right hand panes onto the right hand screen.


   
ReplyQuote
Glenn
(@glenn)
Member Admin
Joined: 8 years ago
Posts: 1926
 

@francisw zip up your latest log and snp file and post here.

I can't read Chinese but I think that's just a corrupted string with no null terminator.

This post was modified 3 weeks ago by Glenn

   
ReplyQuote
(@francisw)
Active Member Registered
Joined: 8 months ago
Posts: 7
Topic starter  

Attached


   
ReplyQuote
(@francisw)
Active Member Registered
Joined: 8 months ago
Posts: 7
Topic starter  

I think I have this solved. I wasn't thinking along the lines prompted by your replies above (that the driver pack names were incorrect & something weird in my set up was causing this).

Despite saying I've had same problem across different versions & machines I've realised I use the same folder, in which I retained older files (e.g. sdio.cfg) to e.g. keep the theme I liked.

I just moved SDIO_x64_R830.exe to a new folder & ran it.  Obviously got no indexes & driver packs etc. but it seems free of the issue. I'll "rebuild" in the new folder.

I should have tried this earlier, can't believe my use of SDIO had been hampered for months by this, when the solution was so simple.


   
ReplyQuote
Glenn
(@glenn)
Member Admin
Joined: 8 years ago
Posts: 1926
 

@francisw The log tells me you have a mixture of SDIO and SDI files.  The SDIO indexes are no longer compatible with SDI.   The driver packs remain compatible.    So a fresh start with SDIO and new indexes should solve the problem.


   
ReplyQuote
(@francisw)
Active Member Registered
Joined: 8 months ago
Posts: 7
Topic starter  

Thank you! (I tried SDI back when "it was yours", then returned after a while, used for a bit & then found out about "the split" & switched to SDIO, but must have retained some SDI filles).

This post was modified 3 weeks ago by FrancisW

   
ReplyQuote
Glenn's Page