I would like to aim towards the Command Prompt or whatever the " true " terminology is for entering in command line commands in XP and newer Versions of Windows.
It's not DOS anymore. The current Windows prompt is Windows CMD.
Quote:
I " presume " that there is other Directories on the disk besides #C:\
These other Directories could be in the form of partitions, i do not know.
Other disks, if present, will be available as d:\, e:\, and so forth. Windows Vista and 7 and probably 8 make special recovery/boot partitions that they won't normally show you but should be visible to other operating systems.
Network paths like \\server\path\to\folder are invalid in CMD.
In Windows XP and newer, you can manually assign a drive letter to a share however:
In older versions, I think it's accomplished with the NET SHARE command.
Quote:
So i will point the question to the whole 110 percent of the Disk that Microsoft resides on, and just what is the true and correct terminology and way to work with the white text on black background is.
I would like to actually see with my eyeballs what there is on the Disk. I am working towards installing Linux on a HP Mini and would like to preserve the XP and its dependencies and associates.
Thank you.
Using Linux is an excellent way to do so actually, since it will not be using any of the usual Windows filters on what you see and will not restrict you from system folders.
I'd suggest booting a Knoppix livecd instead of installing Linux, at least at first, so you can get some experience with it.
Lately I've been trying to fix a 1991 Packard Bell, it's been running fine, but it's eating my memory for fun and taking away my pages. Is it worth my time trying to fix it, and is it possible to put new programs on it? thank you (9 Replies)
Hi, In my MSDOS version on windows'98, many keys are not working. I feel that my version is old and I wnt to update it. Can anyone tell me how can i do so.
Please tell me soon.
Thanks a lot.
-Kinnaree
:confused: (1 Reply)
I know nothing of unix and didn't know where to start. I've heard of a DOS to Unix translator, and since I know DOS pretty well, I thought that this program would be perfect. Any help you could give me would be appreciated.
Bryan (1 Reply)
I had just recently experienced, a bad experience... Apperently, a worm got into my computer a created itself in my MS-DOS. No serious damage was done, but I did a little study on it, through my computer. The virus got thought my scan, by coding itself as an HTML file. Don't know why it did that,... (2 Replies)
I have navigated every DOS and UNIX FAQ to find the DOS equivalent of the UNIX ps command (ps -f would be even better) but all listings of DOS<>UNIX commands do not have it (they all have the same basic commands listed). DOS must have a way of detecting running processes and TSRs. mem /c is the... (7 Replies)
Hi
I have a dos batch file in window server where I call a cmd command for creating some db.
this cmd commad is located in e:\data\abcd\xyz.cmd.
Now I call this batch file from unix ssh.sh but my access point is D in window server here I want to change the dos prompt to e:\data\abcd.
in... (3 Replies)
Hello ;
I have a problem running some script on dos .
when i run :
C: ls /temp
ls: cannot access /temp: No such file or directory
but when i run
C: ls \temp
windriver backup remotebackup
also when i run
C: ls temp
windriver backup remotebackup
The... (4 Replies)
Dear all, I am trying to write a unix shell with C++ that is similar to Windows command line. I planned to call it Dosh (DOS-sHell).That means you can directly run dos or win32 console programs with it. It will be distributed according to the license g GPL. Any advice? (This is my first c++ program... (3 Replies)
About 3 days ago our Apache logs started filling with the following errors:
mod_ssl: SSL handshake failed (server <weberver>:443, client 41.235.234.172) (OpenSSL library error follows)
OpenSSL: error:1408A0B7:SSL routines:SSL3_GET_CLIENT_HELLO:no ciphers specified
These initially were... (1 Reply)
Discussion started by: ccj4467
1 Replies
LEARN ABOUT OSX
cupsaddsmb
cupsaddsmb(8) Apple Inc. cupsaddsmb(8)NAME
cupsaddsmb - export printers to samba for windows clients
SYNOPSIS
cupsaddsmb [ -H samba-server ] [ -U samba-user[%samba-password] ] [ -h cups-server[:port] ] [ -v ] -a
cupsaddsmb [ -H samba-server ] [ -U samba-user[%samba-password] ] [ -h cups-server[:port] ] [ -v ] printer [ ... printer ]
DESCRIPTION
cupsaddsmb exports printers to the SAMBA software (version 2.2.0 or higher) for use with Windows clients. Depending on the SAMBA configura-
tion, you may need to provide a password to export the printers. This program requires the Windows printer driver files described below.
OPTIONS
cupsaddsmb supports the following options:
-H samba-server
Specifies the SAMBA server which defaults to the CUPS server.
-U samba-user[%samba-password]
Specifies the SAMBA print admin username which defaults to your current username. If the username contains a percent (%) character,
then the text following the percent is treated as the SAMBA password to use.
-a
Exports all known printers. Otherwise only the named printers are exported.
-h cups-server[:port]
Specifies a different CUPS server to use.
-v
Specifies that verbose information should be shown. This is useful for debugging SAMBA configuration problems.
SAMBA CONFIGURATION
cupsaddsmb uses the new RPC-based printing support in SAMBA 2.2.x to provide printer drivers and PPD files to Windows client machines. In
order to use this functionality, you must first configure the SAMBA smb.conf(5) file to support printing through CUPS and provide a printer
driver download share, as follows:
[global]
load printers = yes
printing = cups
printcap name = cups
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
public = yes
guest ok = yes
writable = no
printable = yes
[print$]
comment = Printer Drivers
path = /etc/samba/drivers
browseable = yes
guest ok = no
read only = yes
write list = root
This configuration assumes a FHS-compliant installation of SAMBA; adjust the [printers] and [print$] share paths accordingly on your system
as needed.
MICROSOFT POSTSCRIPT DRIVERS FOR WINDOWS
The base driver for Windows 2000 and higher is the Microsoft PostScript driver, which is available on any system running Windows 2000 or
higher in the %WINDIR%SYSTEM32SPOOLDRIVERSW32X863 folder for 32-bit drivers and %WINDIR%SYSTEM32SPOOLDRIVERSX643 folder for
64-bit drivers.
However, currently only Windows 2000 and higher is supported by the Microsoft driver, so you will also need to get the Adobe driver to sup-
port Windows 95, 98, and Me clients. The Adobe and Microsoft drivers for Windows 2000 are identical.
Once you have extracted the driver files, copy the 32-bit drivers to the /usr/share/cups/drivers directory and the 64-bit drivers to the
/usr/share/cups/drivers/x64 directory exactly as named below:
[Windows 2000 and higher]
ps5ui.dll
pscript.hlp
pscript.ntf
pscript5.dll
Note: Unlike Windows, case is significant - make sure that you use the lowercase filenames shown above, otherwise cupsaddsmb will fail to
export the drivers.
ADOBE POSTSCRIPT DRIVERS FOR WINDOWS 95, 98, AND ME
cupsaddsmb can use the Adobe PostScript printer driver for Windows 95, 98, and ME, which are available for download from the Adobe web site
(http://www.adobe.com).
The Adobe driver does not support the page-label, job-billing, or job-hold-until options.
Once you have installed the driver on a Windows system, copy the following files to the /usr/share/cups/drivers directory exactly as named
below:
[Windows 95, 98, and Me]
ADFONTS.MFM
ADOBEPS4.DRV
ADOBEPS4.HLP
ICONLIB.DLL
PSMON.DLL
Note: Unlike Windows, case is significant - make sure that you use the UPPERCASE filenames shown above, otherwise cupsaddsmb will fail to
export the drivers.
KNOWN ISSUES
Getting the full set of Windows driver files should be easier.
SEE ALSO smbd(8), smb.conf(5), http://localhost:631/help
COPYRIGHT
Copyright 2007-2013 by Apple Inc.
8 July 2013 CUPS cupsaddsmb(8)