Results 1 to 13 of 13
  1. #1
    Uranium Lounger CWBillow's Avatar
    Join Date
    Jul 2002
    Location
    Las Vegas, NV USA
    Posts
    6,371
    Thanks
    78
    Thanked 12 Times in 11 Posts

    Mapping Issues (WinXP SP-3)

    I don't understand:

    I'm trying to set up my Winamp, and having issues (a precursor to the issue), so I wanted to map "M" (Music) to "Cocuments and SettingsCWBillowMy DocumentsMy FilesMy Music" (quoptes exclusive); so I set up the folder for sharing.

    But it doesn't show when I go to map it. All my mapping I did within Explorer.

    I've tried shutting everything else down, re-booting.... nothing seems to do it. I have "Cocuments and SettingsCWBillowMy Documents" mapped to "P" with no issues. How com the "M" won't take?

    Regards,
    Chuck Billow
    -------------------------------------------------
    "Good judgment comes from experience, and experience - well, that comes from poor judgment."

    ~ A(lan) A(lexander) Milne (1882-1956)- "House at Pooh Corner"

  2. #2
    Administrator
    Join Date
    Mar 2001
    Location
    St Louis, Missouri, USA
    Posts
    23,593
    Thanks
    5
    Thanked 1,059 Times in 928 Posts

    Re: Mapping Issues (WinXP SP-3)

    First, if you are really running SP-3 it is still BETA and may be part of the problem. Next, is this related to your thread starting 07 Dec with <post:=680,996>post 680,996</post:> or 15 Dec with <post:=682,755>post 682,755</post:>?

    Joe
    Joe

  3. #3
    Uranium Lounger CWBillow's Avatar
    Join Date
    Jul 2002
    Location
    Las Vegas, NV USA
    Posts
    6,371
    Thanks
    78
    Thanked 12 Times in 11 Posts

    Re: Mapping Issues (WinXP SP-3)

    Joe:

    Yes this is a mapping issue, but different. I haven't lost it... I can't set it.

    At first I thought that it may be a "nesting issue", and sine my "My Documents" was aalready mapped, then a folder inside might be... but if that were the problem, then ones I've set up on other machines that were/are nested shouldn't work, and they do.

    Yea, I suppose that it may be influenced by the SP-3, but that is an RC now, so it should be sort of stable, dontcha think? 'Sides, as you pointed out, I had mapping issues long before SP-3 was even on the boards, let alone a Release Candidte.

    There's just some quirk about mapping that I haven't figured out yet and it just keeps rearing it's ugly head every so often...

    Regards,
    Chuck
    -------------------------------------------------
    "Good judgment comes from experience, and experience - well, that comes from poor judgment."

    ~ A(lan) A(lexander) Milne (1882-1956)- "House at Pooh Corner"

  4. #4
    Uranium Lounger CWBillow's Avatar
    Join Date
    Jul 2002
    Location
    Las Vegas, NV USA
    Posts
    6,371
    Thanks
    78
    Thanked 12 Times in 11 Posts

    Re: Mapping Issues (WinXP SP-3)

    Joe:

    On a lark, I just went into a CMD window and mapped the drive using SUBST -- and that worked. I can't recall whether that was also the case in prior circumstances.

    Is there any reason someone wouldn't/couldn't use SUBST instead of doing it through explorer iinstead of "NET USE" or "NET SHARE"?

    Regards,
    Chuck
    -------------------------------------------------
    "Good judgment comes from experience, and experience - well, that comes from poor judgment."

    ~ A(lan) A(lexander) Milne (1882-1956)- "House at Pooh Corner"

  5. #5
    Uranium Lounger CWBillow's Avatar
    Join Date
    Jul 2002
    Location
    Las Vegas, NV USA
    Posts
    6,371
    Thanks
    78
    Thanked 12 Times in 11 Posts

    Re: Mapping Issues (WinXP SP-3)

    Joe:

    I think part of the problem is that the o/s has difficulty with multi-word share names.

    I understand that it is *supposed* to work, but that's twice now that I've changed a name to something almost mono-syllabic, and then the mapping worked.

    Maybe it has something to do with the backward-compatibility that the o/s needs, and that the older o/s's didn't all support multi-word folder and file names.

    ?

    Regards,
    Chuck
    -------------------------------------------------
    "Good judgment comes from experience, and experience - well, that comes from poor judgment."

    ~ A(lan) A(lexander) Milne (1882-1956)- "House at Pooh Corner"

  6. #6
    Administrator
    Join Date
    Mar 2001
    Location
    St Louis, Missouri, USA
    Posts
    23,593
    Thanks
    5
    Thanked 1,059 Times in 928 Posts

    Re: Mapping Issues (WinXP SP-3)

    I do not recall ever having a problem with multi-word share names. Have a few here at work that are just fine. I'm glad you got it working.

    Also, just because SP-3 has been designated as a release candidate does not mean there won't be issues with it. An RC just means that the vendor thinks the software in question is stable enough to get a large group of people involved in the testing. You should never run a beta of anything on a machine you are not willing to have trashed by said software.

    Joe
    Joe

  7. #7
    Platinum Lounger
    Join Date
    Nov 2001
    Location
    Melbourne, Victoria, Australia
    Posts
    5,016
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Mapping Issues (WinXP SP-3)

    Chuck

    Better to be fully aware of what the implications of Release candidate software are. Just because it is believed by the vendor, that no major bugs remain, it doesn't mean that no further will appear - they usually do!

    BTW, I just stumbled across a nice new user pic for you!

    Alan
    Attached Images Attached Images

  8. #8
    Super Moderator
    Join Date
    Dec 2000
    Location
    Renton, Washington, USA
    Posts
    12,560
    Thanks
    0
    Thanked 4 Times in 4 Posts

    Re: Mapping Issues (WinXP SP-3)

    I am currently beta testing a piece of software and we are now using a third "Refresh" of the RC.
    So the first release of the RC was far from being ready.

    Now running HP Pavilion a6528p, with Win7 64 Bit OS.

  9. #9
    Uranium Lounger CWBillow's Avatar
    Join Date
    Jul 2002
    Location
    Las Vegas, NV USA
    Posts
    6,371
    Thanks
    78
    Thanked 12 Times in 11 Posts

    Re: Mapping Issues (WinXP SP-3)

    Alan:

    Great pic! Thanks!

    No, Even I dopn't count on RC's to be 100%... but this issue was a recurrence of one from a time back experienced on SP-2.

    I wonder how many Vista users are wishing that if had remained in beta?

    Thanks again for the pic!

    Chuck
    -------------------------------------------------
    "Good judgment comes from experience, and experience - well, that comes from poor judgment."

    ~ A(lan) A(lexander) Milne (1882-1956)- "House at Pooh Corner"

  10. #10
    Super Moderator
    Join Date
    Dec 2000
    Location
    Renton, Washington, USA
    Posts
    12,560
    Thanks
    0
    Thanked 4 Times in 4 Posts

    Re: Mapping Issues (WinXP SP-3)

    <hr>I wonder how many Vista users are wishing that if had remained in beta?<hr>

    Not as many as YOU would think. The ones that are having issues do not see the problem. It is NOT with Vista but with the old hardware and software.

    Just like when XP first came, very few people moved to it. As a mater of fact, there was a news release a while back, by one of the PC Mags, that stated that Vista sales will be higher at the one year mark than XP was.

    Now running HP Pavilion a6528p, with Win7 64 Bit OS.

  11. #11
    Platinum Lounger
    Join Date
    Nov 2001
    Location
    Melbourne, Victoria, Australia
    Posts
    5,016
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Mapping Issues (WinXP SP-3)

    <P ID="edit" class=small>(Edited by AlanMiller on 15-Jan-08 15:39. )</P>> Great pic! Thanks!

    <img src=/S/rofl.gif border=0 alt=rofl width=15 height=15> Well at least one part of my reply proved useful! Here's a more legible version.

    Alan
    Attached Images Attached Images

  12. #12
    Uranium Lounger CWBillow's Avatar
    Join Date
    Jul 2002
    Location
    Las Vegas, NV USA
    Posts
    6,371
    Thanks
    78
    Thanked 12 Times in 11 Posts

    Re: Mapping Issues (WinXP SP-3)

    Dave:

    That could easily be the case. And the fact that hardware incompatibilities are a major part of the problem is well publicized.

    That really changes not the fact that for a novice such as myself, after being sold a machine from Mssuh sellalot down at the corner, all I want to be able to do is go home, plug it in, and compute away.

    That is not happening as often as it is.

    If the novices and the know-nothing are removed from the market statistics, then the potential may not look quite as rosey, so I would think that these people's experiences would matter. Seemingly not, at least not as much as it should.]

    As for initial problems with prior versions, you're right, they are always there.

    It took me a bit to get used to 95... there are many who say that 98 Second Edition was the "real release", and that 2000 is not much more for the average user than a more stable 98 SE, and that XP was 2000 with eye candy, and now we have Vista, with the much ballyhoo about a promised and then withdrawn all new file system.... Nonetheless, we thrill at the extrapolations and permutations.

    Testing and the attendant issues are part of the scenery for anyone that really likes computers at all... else they would by a simple machine and ten years later it would still be able to balance the checkbook, hold the recipes, and do a family tree.

    And the people like me depend heavily on the people like the WOPR's to keep them on track. I have and do value and use the great advice gotten here. Undoubtedly one of the best, if not THE best board on the net.

    It just seems that the erroneous results that are often trumpeted as the newest and the best are as often faulty in one way or another as not.

    Betas? Or bad publicity?

    But that's just me.

    Mouthing off,
    Chuck Billow
    -------------------------------------------------
    "Good judgment comes from experience, and experience - well, that comes from poor judgment."

    ~ A(lan) A(lexander) Milne (1882-1956)- "House at Pooh Corner"

  13. #13
    Administrator
    Join Date
    Mar 2001
    Location
    St Louis, Missouri, USA
    Posts
    23,593
    Thanks
    5
    Thanked 1,059 Times in 928 Posts

    Re: Mapping Issues (WinXP SP-3)

    Driver issues have been the single biggest problem that people have with Vista. That is not Microsoft's fault. It is a problem created by the original vendors. They had more than enough time to write drivers for the new Vista model. If you carefully read the articles and posts in various forums you'd notice that most of the hardware issues are with older hardware. The hardware OEMs want you to buy their newest stuff so in many cases they've drug their feet on driver development or have just said they'll not come out with a Vista driver for certain old hardware. Then Microsoft gets the blame even though it is not up to them to do the driver development.

    If you or any other novice or a more experienced user buys a new machine and peripherals that are certified for Vista and have problems with the machine (i.e. you can't 'compute away') take it back and make them show you that it does work or replace it. Why drive yourself nuts when the vendor is supposed to support it.

    OTOH, once you start messing with the machine you'd better know what you are getting yourself into. As I posted earlier with any software that is not a production release (no matter what the testing stage) you'd better be prepared to lose the whole machine.

    As far as supposedly 'promised' features go, who promised them to you or anyone else? Neither Microsoft nor any software developer will absolutely promise you that any feature which is leaked early in the development cycle will make the final cut. There can be any amount of publicity, even by BillG, but that still does not mean the feature will perform the way it was expected or be as reliable as was anticipated and therefore will be dropped from a final product. Usually, until you reach the RC stage features can be and will be added, changed, and removed. That is just the way software development goes. Unfortunately, IMO what we are all going to see now is less transparency from Microsoft. They are going to take a page from the Apple playbook and tell us less and less about forthcoming releases. That way they will get bashed less for dropping supposedly 'promised' features.

    Joe
    Joe

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •