Won't know what they are, until they're needed, either. Not cool. I'm still chewing on this unhappy prospect and the only thing that makes sense is that perhaps it's related to microsoft's descent into the ill fated DRM abyss. The failing discs all contained MP3s. Again, not an identifiable failure-inducing trait. Ok, I'll try to keep this short and to the point. No kidding.
Sometimes I want to exaggerate something to get a point across, but I don't have to do that here. And if anyone would like to know what made me better than the guy I replaced, it's an easy question to answer. Feel free to ask. It's not a fault upon the individual, he just didn't know what I knew. I ended up calling Creative Labs multiple times, talking to multiple "technicians" salespeople at Creative Labs.
I knew that DVDs were growing in size meaning more and more data was getting basic on them. The "technicians" were really just salespeople trying to download things and they did not know what I knew. They were used to talking to other technicians that did not read up on the latest events in DVDs I ended up with a subscription to some engineering journal that was oriented to engineers in the msddn field and the articles at that time talked about CD 6.0 DVD formats.
It was the hardware that was faulty and the sales people baic no clue at what was going on in the DVD market. The numbers are probably not exactly correct, so take it just as a description to give an idea of how the DVD technology developed. The DVD format was not the only problem. Then there were some CD writers sometimes a whole model line that could only read the CDs fisual created, other Msdn players visual unable to read the CDs created by those bad "models" or "drives".
Those CDW drives were a major pain to deal with and downlload were alot of them out there manufactured under a whole bunch of different names most were unknown "no name" cheap drives but some others carried labels by well-known companies, i. Creative Labs. Then do a series of write tests, where you write to a DVD or CD and then test that media in an old Windows 9x system to see if it can read it, and then test it in another system. Two or three different machines.
If all read well, you've probably got a great drive and have no worries. At least that's based upon my own personal experience. If one of the other drives can't read the disk, take the new drive back as soon as possible and ask for a replacement. It's a pain in the rump way to do things but that's the only way to do it, as far as I'm concerned.
Testing to make sure msvn older systems can read and copy from a FULL data disk is a requirement. Test the audio burn and playback as well. And for DVDs, the video recording and playback is a must as well.
Trust no one? Trust no one. Test everything. And one last thing I'll mention, is that burners may write very well at the lower speed settings and then go to hell when you try to get them to write at their "fastest" setting.
WinWorld: Microsoft Visual Basic
So be prepared to do ALOT of returns if you're testing things on their "fastest" write settings. I've seen a few drives that don't work at their fastest settings but work very well at slower settings. So whatever X they put on the drive may be a lie and if you're buying cheap drives be prepared to use something lower basic their advertised fastest speed. It's a good idea to test all purchased readers. All disk drives fall into this special class of goods, but my own personal experience really indicates that special tests need to get performed to determine if a new drive really works.
Is there anything I can do with the cdd from my old download I've tried copying them across the network into an identical directory structure, but when I try to execute HELP from within VB 6, it says the files are missing. Something to do with the setup script I guess. Any tricks anyone? Thanks "MikeD" wrote:. None that I know of. The thing is, there are support DLLs that need registered and other entries in the Registry that must exist. Not intending to be mean or come down on you in any way, but how can you lose something so important?
It wouldn't be easy, but it wouldn't be impossible. Through diligence examining the folders, dependancies, and registry, it should be possible to do it manually. Good Luck. I'd think that at least you'd then have the tools for displaying help. On my machine the. You might have to figure out some missing registry settings if it doesn't work straight bassic but that should be made much easier by having a visual machine to examine.
Toy Poodle Buyer? Tough Poo, Bonehead? Total Porridge Burnout? Tricky Panda Bugler? Ticklish Pig Boycott? Truculent Pomeranian Biscuits? Tinned Pickled Beets? Tom Passes Beans? Tender Pudgy Barmaids? Typical Programming Blunder? The initials "TPB" mean ever so many things to me. I don't think you can. I don't think it's actually free. That msdb lack a few of the final updates, which the ideal October MSDN Library visuql would have, but it includes exactly what you asked for.
Bob Hardly free, I hesitate to add. Why are you pointing him to windows API documentation? Oh my, that's hysterical.
WinWorld: MSDN VS
Rather than get the SDK's from Microsoft, you wait till you see something somewhere else. Another link requires installing the WGA spyware.This is the MSDN documentation for the Windows API, MFC, ATL, WTL, Visual Basic, J++ and InterDev as shipped and available in Visual Studio Sep 18, · Download the MSDN Library for Visual Basic 6. Alternatively, you can download 3 separate ISO files for CD-ROMs. NOTE: the total download is about Gb so it will take 20 minutes or so on a 1Mb/sec connection. Extract the MSDN Library Installation. STEP 1: Go the location where the download is located. Apr 26, · Mainstream Support for Microsoft Visual Basic ended on March 31, However, we are releasing this non-security related package because it contains improvements that were ready for release just prior to the end of Mainstream Support. Microsoft Visual Basic has transitioned to Extended Support which runs through March 31,
Maybe MS had that, too. I don't know. But I'm not surprised that it was easier to find on a 3rd-party site than it was on microsoft. You're kidding us all right? How off topic can you possibly get? I actually only downloaded the newer version out of curiosity, as I like to avoid code that won't run on Download, so I don't need updated docs. But to the visual that I looked over the SDK it seemed to include most older docs. It at least beats trying to find information on the MS website, which often requires slogging through 3 or 4 unnecessary msdn for each basic of info.
It's much easier to just use Google rather than the MS site. Their site is disorganized, there are loads of dead links, and their search is very poor. And for anyone 6.0 high-speed the MS pages are completely unusable. It just takes too long to download bloated, 65 KB, superfluous pages that often end up containing only 3 lines of actual text.
I know you don't care about any of this, Mr. Bill, but sometimes your nonsensical posts provide convenient segues to provide more info. Which isn't VB6. Hey why don't we include. NET in there too, I'd bet you'd like that .
Actually no it doesn't because the VB6 documentation is only available online if you don't have the original CD's. As to the rest of your rant, I'm sure you thought it was cute, but it was just completely off topic to the original question. Even if we were to assume you honestly somehow thought the original poster was hasic API documentation for Windows, you should have pointed him to current versions or asked for which version of windows etc, instead of picking some download that wasn't even on Microsoft's site.
As others have posted here, finding the SDKs for download from Microsoft's downloads downkoad incredibly easy once you decide which of the many SDKs you want. But back to the topic, none of them other viwual msdn subscriber downloads contain the VB6 documentation.
Download Microsoft Visual Basic Common Controls from Official Microsoft Download Center
This dotnet crusade of yours is really gettin' to you, isn't it! Just let it go, sonny. Go back to your sheep. Reply to author. Report message as abuse. Show original message. Either email addresses are anonymous for this group or you need the view member email addresses permission to bwsic the original message. Hi All, From where can i download msdn help setup for vb 6.
Raj wrote Jeff Johnson.
Vb MSDN Setup file download.
Robert Morley. Which is kinda sad, really. Ken Halter. Karl E. Anyway, that one's got 16 sources currently, most of whom appear to be mass uploaders, as I started downloading from 6 different people within moments of adding the file. Noticeably, most of them are in China where I believe copyright law doesn't apply or at least isn't respected. Does the ISO standard.
What can I say I only got my first burner about a year ago, and I think I've used it twice so far, so I'm not exactly conversant with the technologies surrounding it. Thanks, Jeff. Galen Somerville. Okay, so given compression, 1. Given the number of people in China who had it, though, I hope it's in English for anybody who needs it! C Rule.
I don't see where you found it from that link and I need it too. Hope you don't mind spelling it out for me. Stefan Berglund. On Wed, 11 Jul"Karl E. Jim Carlock. After version 6, Visual Basic was replaced by Visual Basic. NET, an incompatible successor. Microsoft Visual Basic 6. It was extremely popular, and is still used in many businesses.
Download MSDN Library for Visual Basic 6
It is the last that can create native bit applications for Windows 9x and NT. The replacement product "VB. NET" requires Dot Net, dowload changes the core basic language in such a way that it is difficult to port VB 6 applications. Visual Basic easily interfaced with many database products most notably Microsoft Access and reporting tools most notably Crystal Reports Visual Basic 3 was the most popular version under bit Windows 3.