-
Posts
-
By David Uzondu · Posted
Elon Musk once again claims Tesla robotaxis are coming soon by David Uzondu Image via Depositphotos.com Tesla's CEO, Elon Musk, has announced a tentative start date of June 22 for the company's long-awaited public robotaxi service. According to a post on his social media platform X, the initial launch will be in Austin, Texas. Musk added a significant condition, however, saying "We are being super paranoid about safety, so the date could shift." The service is expected to begin with just 10 to 20 Model Y SUVs operating within a limited area and with remote human supervision. He also mentioned a plan starting June 28 for new Teslas to drive themselves from the factory to a customer's home. This is a moment many are probably waiting for, though it comes with a heavy dose of skepticism. Musk has made grand promises about self-driving before. This robotaxi network brings to mind the bold claims from all the way back in 2019 when the company said a similar service would launch the following year. That evidently did not happen. Federal regulators also have their doubts. Last year, the National Highway Traffic Safety Administration criticized Tesla for making its "Full Self-Driving" feature sound more capable than it actually is, demanding the company align its marketing with reality. Tesla is also driving into a field that is no longer empty. Waymo, Google's sibling company, is already a major player, offering hundreds of thousands of paid rides per week across Phoenix, San Francisco, Los Angeles, and even Austin. The company is so far ahead that it has begun testing in Tokyo. But being ahead means Waymo is also the first to face certain dangers. For example, on the evening of June 8, a group of protesters in downtown Los Angeles summoned Waymo vehicles during a demonstration. When the vehicles arrived, they slashed the tires, smashed the windows, and spray-painted the cars before setting three of them on fire. Which raises a thorny question for Tesla: if you can summon a car with no one inside, can you summon it just to destroy it? It's one thing for protesters to stumble upon a robotaxi and vandalize it; it's another for someone to use the app to call a driverless car to a secluded spot for a planned attack. With public sentiment around Musk so divided, especially given his DOGE shenanigans and his recent face off with Donald Trump, that's not just a theoretical problem. We've already seen this hostility play out in attacks where people vandalize Teslas, carving swastikas into them and spray painting slogans like "Burn More Teslas" on walls. -
By BoondockSaint · Posted
This is actually quite useful. But why wouldn't they implement this in the local file system? The code is obviously all there now... maybe in 5 years. -
By pelaird · Posted
The new "Story Cards" in the Software section are nice, but I wish they had the product icon included. I use this section to identify updates for software that I use regularly, and it's sometime difficult to identify the software without the product icon. Thanks for your consideration. pelaird -
By Eyevou · Posted
Mozilla really needed to focus on their core product for a while now. I will not mourn the death of pocket or AI garbage. One thing they don't do that I believe they should is advertise more, and not just to their core audience, especially their additional services. Let people know they actually exist. -
-
-
Recent Achievements
-
Food-Beverages-Nutrition earned a badge
Week One Done
-
Tech Dogs earned a badge
Week One Done
-
computerdave91111 went up a rank
Enthusiast
-
.thumb.gif.f3db843d695937470f064e60ad930b48.gif)
Falisha Manpower earned a badge
Week One Done
-
elsa777 earned a badge
One Month Later
-
-
Popular Contributors
-
Tell a friend
.thumb.gif.f3db843d695937470f064e60ad930b48.gif)
Question
komplexnous
This is extremely annoying!!! I use MobydockDX (get it at www.mobydock.com), and I keep getting a VSS error when my family uses AOL on this computer (P4 2.4B; GeForce4 Ti4200 8X 128MB; VIA P4PB Motherboard; 512MB DDR RAM). I hate AOL, but my computer should be able to handle it (with no %$@#&*% errors!!!) even if it is lousy software!!! When AOL closes, MobydockDX does as well!! When I look at WXP's Event Viewer, it tells me that there is a VSS Error coupled with an EventSystem Error then the application error with MobydockDX!!
Here are the errors in event viewer leading to the closing of MobydockDX (in order) :angry: :
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043C from line 44 of d:\nt\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206.
Windows saved user MACHINE\Komplexnous registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043C from line 44 of d:\nt\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206.
Windows saved user MACHINE\Komplexnous registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.
The COM+ Event System detected a bad return code during its internal processing. HRESULT was 8007043C from line 44 of d:\nt\com\com1x\src\events\tier1\eventsystemobj.cpp. Please contact Microsoft Product Support Services to report this error.
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x80040206.
Windows saved user MACHINE\Komplexnous registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.
Faulting application mobydock.exe, version 0.8.7.0, faulting module d3d9.dll, version 5.3.1.902, fault address 0x000932a4.
:cry:
I have tried disabling VSS and the Event service and COM+ service, but the same problem occurs. I have also tried the Microsoft fix to pop in the XP CD to start with it, then hit enter to install it, then hit R to fix the installation (not in the XP environment). It fixed my problem for a while, then....wait!!
I just remembered something. I installed the 45.23 Nvidia video driver when I did this fix, and I just updated to 53.03....this may be the problem (the new driver).
However, I am still going to post this in the event that downgrading my driver does not fix the problem, which is will most likely happen. I will also try to use Y'zDock, Objectdock, or something instead of Mobydock for a day or two to see if the software is buggy (it is beta), but last time I tried this, the error was still in the Event Viewer. :unsure:
ANY help WILL be appreciated!!!!
Thank you to anyone who reads and/or responds!!
Link to comment
https://www.neowin.net/forum/topic/127796-windows-xp-volume-shadow-service-error-vss-error/Share on other sites
2 answers to this question
Recommended Posts