Home > Cannot Start > Cannot Start With Forward Slash Or Back Slash

Cannot Start With Forward Slash Or Back Slash

Does anyone know when that change occurred? SSI is executed before ASP. The disk shows as healthy in Disk Manager, and scandisk or what's-its-name runs successfully. And DOS had much better IDEs, like Turbo Pascal. ;) I hypothesize that originally Windows accepted only the backslash, and then at some time it changed to accept the forward slash Check This Out

Hi Steve, Every version of Windows has accepted "/" as a path separator. I had no problem using include virtual on my machine (and strangely enough, I'm using Win ME and PWS too!). You have two sections of the code to deal with the application and the session, so you would have to figure out whether the code your dealing with is for the Join our community for more solutions or to ask questions. learn this here now

Or doesn't it show up at all? (how do you know it exists? Oct 20, 2010,17:51 #8 webber123456 View Profile View Forum Posts SitePoint Guru Join Date Jun 2007 Posts 691 Mentioned 0 Post(s) Tagged 0 Thread(s) There are two ways to include files Modern software tries to automatically correct you when you type the wrong type of slash, so it doesn't matter which type of slash you use most of the time. Get downloadable ebooks for free!

have you tried include virtual? Former ASP Forum Moderator - I'm back! And good luck. Andrew Last edited by awasson; Oct 24, 2010 at 14:06. My copy of Norton's Guide to the IBM PC makesthe explicit statement that directories were directly influenced byunix.

When MacOS was introduced, it used the colon character. Privacy Policy. My guess is that it is being taken as... https://www.experts-exchange.com/questions/21032889/include-file-header-inc.html See, under DOS there's this great utility called "unerase" which can be used to recover files accidentally deleted.

Reply With Quote 10-19-2002,06:13 PM #2 whammy View Profile View Forum Posts Senior Coder Join Date Jun 2002 Location 41 8' 52" N -95 53' 31" W Posts 3,660 Thanks 0 i the file that gives the error is in the includes folder, which is in the root web. The problem in Win98 for me came from saving web pages with extra LONG file names .... -- Cousin Stanley Human Being Phoenix, Arizona Jul 18 '05 #25 P: n/a Stephen I don't think 1.0 had a hierarchical filesystem at all did it?

either, because it gives me this error:The Include file '..\forum\includes\consts-inc.asp' cannot contain '..' to indicate the parent directory. But the Windows and DOS kernels are happy with either "\" or "/". -Mike Jul 18 '05 #6 P: n/a Andrew Dalke Bob Gailer: Good question. Doug G ===== "If you ain't the lead dog, the view is always the same - Anon Oct 20, 2010,01:56 #3 siteguru View Profile View Forum Posts SitePoint Wizard Join Date Seriouslyannoying.

the forum folder is also in the root web. his comment is here You can usually forget that there are two different types of slashes, but it occasionally does matter. First Name Please enter a first name Last Name Please enter a last name Email We will never share this with anyone. I want to perform at cranial activities with visi.com Tuesday Weld!!

Only I would deliberately delete a file in order to probe the system; eg, is this file really used? They can be deleted with no problem under DOS .... You cannot delete other topics. http://culturahq.com/cannot-start/cannot-start-with-forward-slash-or-backslash.html IIRC that is or was a bug on (some) Windows versions: the path+filename you have to pass to the Delete File API function could be too long for the reserved string

I hypothesize that originally Windows accepted only the backslash, and then at some time it changed to accept the forward slash as well. I have an include on this asp page now, it gives me this error: File attribute '\forum\includes\consts-inc.asp' cannot start with forward slash or back slash. The fun you can have on windows, I've managed to create files that cannot be removed :-) Ronald Jul 18 '05 #18 P: n/a Stephen Horne On Fri, 26 Sep 2003

I think I'll tackle include files first.

Python automagically determines the path component separator, os.sep, and uses it for most file path transformations to and from the internal language's '/'. Is this perhaps what gives you the The following does work for me E:\dalke>cd .. Reply With Quote 10-19-2002,10:52 PM #5 whammy View Profile View Forum Posts Senior Coder Join Date Jun 2002 Location 41 8' 52" N -95 53' 31" W Posts 3,660 Thanks 0 But I thought I'd ask the most erudite group that I know... :-) When did Windows start accepting the forward slash as a path separator character?

This doesn't work everywhere in Windows, however. Includes in libraries Browse more ASP / Active Server Pages Questions on Bytes Question stats viewed: 1540 replies: 3 date asked: May 10 '06 Follow this discussion BYTES.COM 2016 Formerly Directly influenced, yes - but as DOS 1 didn't have subdirectories but did have options marked with '/', the unix subdirectories couldn't be duplicated exactly in DOS 2. navigate here It was?

for some information. Privacy Policy Site Map Support Terms of Use Jump to content Sign In Create Account Search Advanced Search section: This topic Forums Members Help Files Calendar View New Content At one time, it was accepted as a truism that Windows (like MS-DOS) was different from Unix because Windows used the backslash as the path separator character, whereas Unix used the Register.

Always have. * None of the standard command shells (CMD or COMMAND) will accept forward slashes.

  • © Copyright 2017 culturahq.com. All rights reserved.