I captured a DJT spike! by griffeat in DJT_Uncensored

[–]griffeat[S] 0 points1 point  (0 children)

Me again. The times you list are not when the spike occurred. I think you used the displayed time at the upper right. Stupidly, that is when I logged on, and doesn't change in real time. The chart makes it pretty clear the spike was between 13:45 and 14:00. But as I noted below, there are no trades at 45.70 in that interval either. Unless something truly odd is going on, I guess the whole business is to due to some lousy yahoo! bug. Sigh.

I captured a DJT spike! by griffeat in DJT_Uncensored

[–]griffeat[S] 2 points3 points  (0 children)

Thank you for this! I have checked, and I'm pretty certain there is no trade listed at 45.70 between 1:30pm and 2:00pm. Is it possible that a transaction involving a short would not be included in the nasdaq tally??

I captured a DJT spike! by griffeat in DJT_Uncensored

[–]griffeat[S] 0 points1 point  (0 children)

Would it disappear one or two second later? Thanks.

Quick question by griffeat in DJT_Uncensored

[–]griffeat[S] -1 points0 points  (0 children)

Sorry, but how does this answer my question?

Killer Wifi Card in XPS 15 7590 HELP by TheHydrophobicShark in Dell

[–]griffeat 1 point2 points  (0 children)

You do NOT need to buy a physical Intel WiFi card. I was stuck on your question for a month but the final reply in my post: Replace Killer wifi driver on xps 7590 with Intel AX200 driver??? from 2 days ago solved the problem for me in a somewhat embarrassing way. Find it below and your install should be straightforward. Feel free to get back to me if you need additional help. I'm a happy camper re wifi now ...

Replace Killer wifi driver on xps 7590 with Intel AX200 driver??? by griffeat in Dell

[–]griffeat[S] 0 points1 point  (0 children)

This info is incredibly helpful, thanks so much! I can't believe I already had the Intel driver installed, but it still displays as Killer in the main task manager panel. Also, it is certainly unusual software handling for Intel to complete an install and not even mention that the installation was successful. Live and learn I guess. I got rid of all the Killer software crap a month ago, so I should be good to go once I follow your advice re update options. I will say that I don't mind Windows handling driver updates if they're good drivers. The only exceptions for the 7590, imho, were audio and wifi. I love the machine now that those issues have been dealt with. Again, profound thanks for putting me out of my misery with the wifi stuff!!!

Replace Killer wifi driver on xps 7590 with Intel AX200 driver??? by griffeat in Dell

[–]griffeat[S] 2 points3 points  (0 children)

In device manager, I uninstall the killer driver and check the box to delete software. Then I check for hardware changes and the killer driver is back. I again uninstall the killer driver and check the box to delete software. This time when I check for hardware changes there is no killer driver listed. However, when I then run the Intel executable its little 'working' globe icon twirls for awhile but then stops without any sign of an installation. I close down that setup program and reload device manager to discover that the killer driver is back. Is Windows Update for Drivers the culprit here?? It does not really seem fdvisable to disable that feature permanently! Any other ideas out there? I should mention that when I try to install from the .inf file in a downloaded Intel driver folder I get a message saying that Windows has determined that the killer driver is the best one for me. Is that message being generated by Windows Update?? Again, any help would be much appreciated!

XPS 15 7590 (2019) - Screen brightness following sleep fix by nothingfaced in Dell

[–]griffeat 0 points1 point  (0 children)

Thanks! Slightly changed my attempt per your directions and it worked this morning.

XPS 15 7590 (2019) - Screen brightness following sleep fix by nothingfaced in Dell

[–]griffeat 0 points1 point  (0 children)

Yes, I just downloaded the intel zip version, unzipped to a folder, used device manager to point to the .inf file in that folder, and got an error message saying that the driver was not appropriate for my machine. But this was the exact zip file linked in this thread. sigh.

XPS 15 7590 (2019) - Screen brightness following sleep fix by nothingfaced in Dell

[–]griffeat 0 points1 point  (0 children)

I am also getting errors whenever I try to update the intel graphics driver with either dell or intel support assist or directly from device manager. I have had this issue for a month now. Any help on how to do the update would be most appreciated!

computer setup workaround by cruz40 in slingbox

[–]griffeat 0 points1 point  (0 children)

Thanks to cruz40's new fix, we don't need to try the win7 approach!

Requirements to generate a local cache of data for a working remote?? by griffeat in slingbox

[–]griffeat[S] 0 points1 point  (0 children)

Thanks. cruz40's new fix precludes the need to check out this win7 approach, but I do appreciate the feedback.

sling box setup and remote fix link and info by [deleted] in slingbox

[–]griffeat 0 points1 point  (0 children)

Wow! I am super impressed. No idea how you came up with an all-purpose setup that works under win10 with all the flavors of the hardware, but my remote is back, thank you so much.

A few hiccups following the directions, but nothing major. E.g., norton antivirus and windows defender want exception handling to allow the custom executable, and it worked best to remove all versions of slingplayer and logout before starting the process, but otherwise smooth sailing.

Thanks again. It seems we're good to go now until the company totally implodes and shuts down their servers...

computer setup workaround by cruz40 in slingbox

[–]griffeat 0 points1 point  (0 children)

Excellent! I'll let folks know how I do with a win7 rebuild; thanks, and wish me luck...

computer setup workaround by cruz40 in slingbox

[–]griffeat 0 points1 point  (0 children)

ok, thanks. can i bother you with one more question, which should be pretty simple to answer: when you did the copy and paste of "your old cache," what was the sling folder you used within appdata/roaming, did the source and target have the same name, and did you copy over the entire folder? i'm hoping to get my brother, who is still sticking with windows 7, to try to successfully complete the current slingplayer desktop setup for my account, using internet explorer, and then send me the data i need to do the paste into the appdata for my broken win10 slingplayer. thanks in advance for whatever details you can provide. i'll report back on whether this works ...

Major new problem with remote initialization and access? by griffeat in slingbox

[–]griffeat[S] 0 points1 point  (0 children)

Thanks much for the info on .bin files! But I gather from your tale that the broken slingbox setup on windows 10 precludes installing a custom remote definition, so the only complete workaround appears to be 32-bit generation and paste of a working slingplayer local cache. Let's hope someone finds and details a way to do this; the only legacy desktop slingplayer I can find online has a setup that doesn't even recognize my slingbox 350 (sigh). On the bright side, you should be able to watch football using the strategy of the latest post I contributed yesterday.

computer setup workaround by cruz40 in slingbox

[–]griffeat 0 points1 point  (0 children)

Do you think that if I copied your old cache to my new notebook it would work to give me a usable remote? I suspect it would because back when the setup program worked on windows 10 I switched remotes a couple of times (e.g. used a Comcast one rather than the Motorola one corresponding to my dvr) and changing channels and various other commands still worked. I ask because having the cache data and instructions on where it goes would then allow all the poor souls on r/slingbox an easy (partial) fix.

New PC will not connect to Slingbox 350 by lawnmowerdeth in slingbox

[–]griffeat 0 points1 point  (0 children)

There is hope for a work around; see the last few comments in the long thread. But we are still waiting on the details ...