Windows 7: Documents Library Not Functioning

One of the helpful mods got to it first

LOL..they're good ones!

Anyway, I got it figured out.
It's not the data in the SearchConnectorDescriptionList tag, it's all the info in the Serialized tags that needs to go. It's rebuilt machine specific automatically as soon as you close the file. It just took nother xml file to see what I needed to do and I found Brink still on line and he sent me his.
It's rebuilt and functioning now so if we run across others that have this issue, we can rebuild it for them rather easily now. We can get them to post their file and we can show them the edits and tell them how and where to find their own additions to make it work.

Great work and help Barrod! Your Rep has been upgraded!!

I tel ya tho...the more I use Libraries, the more I LIKE this new function of Windows 7. It's handy and fast to access many different locations from one Library group, really makes findng things faster.

That's great! Its good that you got the OS problem sorted out.

Have taken the time to look at the post you made and the forum threads on your X-Fi Crackling and Popping issue.

Will try to see if we can find other solutions for you and will be posting on that thread if I got something.

Cheers

@Chappy:

Attached are ALL my Libraries for you to check whatever it is you wanted to check, as asked.

Hope this helps.

Hey Nos

I remember some others had this issue with Creative cards too, I'll have to check my history and see where I read about them. Seems to me someone had a temp fix until Creative release a Windows 7 driver. I'll read that post and see what we can find

@ Peter - Thanx again Bro!
As Barrod found, they are rather simple XML files and somewhat interchangeable (to a point). The resource pointers of course need to be specific to the library type so the icons are proper, and the User ID is user specific, but after that all you need do is delete the serialized tag info so it can be rebuilt when the file closes.
It's actually quite a simple but very effective little extensible file MS made for these libraries, and I'm thinking of some other things I can do with one of these as a template starter. There are some interesting possibilities

Hmmm... Now that you mentioned it, I believe you're right Dave.
I can't remember what kind of issue that was with a that Creative card as well

Thanks Dave.

The first thing I did after I exhausted my own troubleshooting ideas was to search these forums for possible fixes. I tried all I could find (see my original post above). If you see any I've missed, please let me know.

In the mean time, I found Creative's bug list for these beta X-Fi drivers. One user isolated a similar problem on his system by reducing his RAM to 3 GB, at which point the problem disappeared. (However, he was running XP64 with different processers, motherboard, and X-Fi model.) I tried removing the ReadyBoost RAM on my system to no avail - not surprising since I still have 6 GB of RAM installed on my motherboard. So, my problems could possibly be related to driver bug in the addressing of system RAM above 3 GB, or latency in the handling of bus master memory requests on my nVidia nForce4 motherboard as noted in the Creative article referenced in my original post, some combination of the two, or something else entirely.

In the mean time, I'm soundless, since sound quits within 1-5 minutes, infrequently preceded by one or more very loud screeches.

Any ideas for temporary fixes/workarounds to restore undistorted sound? Otherwise I fear I will remain soundless until commercial release (hopefully containing fixed Creative and nVidia drivers)!

Thanks again for everyone's help.

Dale

P.S.
I've reported my issues and system details on the Creative Bug List.

You could try reducing your RAM to 3GB temporarily to verify if that's the cause. If it is there used to be a way to limit driver address space that I think I could dig up again. Let's start by making sure that's the root cause. Open Start, type "msconfig", select Boot tab, click Advanced options, select Maximum memory and enter "3072". Reboot, see if the problem persists and post back, please.

THANK YOU, Baarod! Using msconfig to limit RAM virtually eliminated the interference and ultimate sound loss. (I can still hear an occasional crackle or pop or drop out.) (Note: I left ReadyBoost enabled.) Now, if you can only remember how to limit the memory address space for this driver so I still have all my RAM for application/multitasking use.

Device Manager is showing using an unshared IRQ (one of the first things I checked) and the Memory Ranges 00000000D5E00000 - 00000000D5FFFFFF and 00000000D8000000 - 00000000DBFFFFFF.

Thanks again,

Dale

Dale,

Can I get a screenshot of device manager showing that information please?

Mike

P.S. Glenview? I'm down in Bradley -- near Kankakee...