Jump to content

DiGGiTY

Member
  • Posts

    157
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Posts posted by DiGGiTY

  1. I want to add a .jpg to my signature (presently it is just text), so I linked to the file which I placed on my public web server using %7Boption%7D tags in my signature. Of course, the problem is that the image isnt showing up. Its 300x100 and 7K in size.

    Thanks in advance...

  2. This is just a stab in the dark, but if there are any other electric motors or large magnets (speakers) near the monitor, you should move them.

    More likely though, the monitor is messed up from a hardware perspective. Never, ever try to repair a monitor yourself--it is dangerous for a beginner.

  3. First things first--the remote computer you are attempting to attach to must be accessible from your home network. In most cases, unless the computer is in the company's DMZ, the firewall is blocking NetBIOS over TCP. This means that a [net use * \\computername\sharename] will NOT work.

    If all you need is a command prompt on the remote computer, you can open up the firewall to allow Telnet traffic.

    If you want the full desktop experience, connect using Remote Desktop. To enable this, open up port 3389 on the firewall.

  4. use the label command...

    LABEL [drive:][label]

    LABEL [/MP] [volume] [label]

    drive: Specifies the drive letter of a drive.

    label Specifies the label of the volume.

    /MP Specifies that the volume should be treated as a

    mount point or volume name.

    volume Specifies the drive letter (followed by a colon),

    mount point, or volume name. If volume name is specified,

    the /MP flag is unnecessary.

  5. If you were running linux, I'd say use Webmin (http://www.webmin.com). You may have to assemble a few different tools to get the job done.

    The alleged high bandwidth consumption issue is just that--alleged. You take up just as much bandwidth or more surfing any web site.

    If you want a full-featured solution, go with RDP Web Connection. VNC sucks--it's free, but the screen refresh is choppy at best. It's like playing Doom 3 on a 64MB GeForce MX400.

  6. I did some work with a few OEM's, and Microsoft's OEM System Builder page recommends using one of two methods:

    1. Use WinPE, diskpart, and then format

    CFGDISK.CMD

    -------------

    DISKPART /s DISKSCR.TXT

    FORMAT C: /fs:ntfs /q /v:"" /y

    -------------

    DISKSCR.TXT

    -------------

    select disk 0

    create partition primary

    assign letter c

    -------------

    2. Use FDISK, OFORMAT, and CVTAREA

    Use the FDISK utility to create a single disk partition.

    Use the OFORMAT utility to format the disk and properly align FAT clusters.

    Use the CVTAREA utility to create a reserved contiguous file for use in the conversion from FAT32 to NTFS.

    Use the new Windows XP version of the CONVERT utility to convert the volume to NTFS.

    Here's a link you to information on the preinstallation procedures that you can access without being an OEM:

    http://www.microsoft.com/whdc/system/winpr...preinstall.mspx

    Imaging Stuff

    ==========

    The difference between different imaging tools is in reliability, speed, and programmatic nuances. Here's all you need to know--use Ghost--it has been around forever and works like a champ. Symatec actually bought the company that originally developed it, so its got soewhere between 8-10 years on the market.

  7. The P4 3e (Prescott core) will benchmark higher than the P4 2.8 (Northwood core). Comparing to AMD the P4 3e performs like an Athlon 64 3000+/3200+ while the P4 2.8 compares with the 2700+.

    Also, the Prescott core is the future, whereas Northwood will eventually be discontinued. I'd go for the P4 3e.

    If the price difference is bugging you, look at AMD.

  8. Here's the skinny... When you copy NTFS files from one volume to another, no permissions are carried forward--especially on disconnected networks.

    I'm assuming that you burned the files to a CD, USB Stick, or Floppy. Then you copied the files to your PC.

    When the copy occured, permissions were inherited by the parent folder.

    Here's how to get out of this.

    1. Right-click the folder and select Properties

    2. Select the Sharing tab

    3. Select Do not share this folder

    4. Select the Security tab and then Click the Advanced button

    5. Click the Add button and select the user you are logged in as

    6. Give this user Full Control permissions and make sure to check the box at the bottom that says, "Replace permission entries on a child objects..."

    Also, you may be blocked by a Deny permission somewhere.

    7. Make sure that the SYSTEM account also has Full Control

    8. Remove all other accounts

    Hope this helps you out

  9. We'll you're on the right track. Stay with it. I've been in the business for 12 years and I can tell you, none of my friends pull down even close to the kind of money we can make in this gig.

    If you ever need anything, let me know. I'm very well connected in the industry. I wrote the book, Planning for Windows 2000, for Macmillan/New Riders Press and currently work as a consultant for IBM's Microsoft Technology Consulting division.

    Keep at it, and don't get sidetracked. Remember that this business is all about real-world experience--just get your foot in the door somewhere. If you're in the Chicago area, let me know--I can try to hook you up.

    Peace,

  10. The only solid solution I am aware of is the Remote Desktop Web Connection. Remote Desktop Web Connection is a Web application consisting of a COM component and a sample connection page. When you deploy Remote Desktop Web Connection on a Web server, you can provide client connectivity to Terminal Servers and other computers using Internet Explorer and TCP/IP.

    Windows Server 2003: Windows Server 2003 includes an updated Remote Desktop Web Connection that supports RDP 5.2 and is backward compatible with RDP 5.1 and 5.0.

    Windows XP: Windows XP includes Remote Desktop Web Connection, which is an updated version of the TSAC. Remote Desktop Web Connection supports RDP 5.1 and is backward compatible with RDP 5.0.

    Windows 2000: The release of the Terminal Services Advanced Client (TSAC) as a ValueAdd component on Microsoft Windows 2000 Server SP1, extends Terminal Services technology to the Web. The Terminal Services client-side application only needs Microsoft Internet Explorer, a connection to the World Wide Web, and appropriate rights to view Microsoft ActiveX controls. The TSAC supports Remote Desktop Protocol (RDP) 5.0.

  11. I'm sure it can read and write just find to FAT32...  but doesn't it use a 64bit file system to run?  Just like Windows XP will read FAT32 even if it's NTFS.

    The operating system files for Windows XP Professional (32-bit) can reside on either FAT32 or NTFS v5 or higher. Windows Professional x64 must be installed on a GPT partition (legacy partitions are known as MBR or master boot record partitions).

    The GUI in WinXP x64 only allows you to create NTFS volumes within a GPT partition. However, you can create a FAT32 or FAT partition from command line. These plain old FAT partitions are mounted, but not exposed--theycan only be accessed programmatically.

    If you want to read up some more on this, check out this link:

    http://www.microsoft.com/whdc/device/storage/GPT-64bit.mspx

×
×
  • Create New...