clutch
Moderators-
Content count
3857 -
Joined
-
Last visited
-
Days Won
1
Everything posted by clutch
-
Very much so. You get a "box" of tools in the traditional panels that are on the right side of most Adobe products, and you simply drag and drop whatever you want to use. If I need to do a quick layout, I use that first as it works really well. I will also do some ASP coding in it occasionally (though I use Visual Interdev for anything with "depth" to it), and it will connect to databases as well. If you are looking for an app that can get people up and running quickly but will not be easily outgrown, then that's the one I would recommend. To me, it's what Dreamweaver/Dreamweaver UD should have been in the first place.
-
Good luck dude, because I have no idea what it is. Both of the suggestions made here have worked for me every time, that's why I find your problem puzzling (especially with a card like that, I was half expecting some "Oak Technologies" or "Number Nine" throwback ).
-
Well, while relaying "THE FACTS!!", how about telling us what kind of video card you are using.
-
Consoles are nice, I would just like a platform that supports the games I want to play. Unfortunately, I have seen games that I like across multiple consoles and I don't have the desire to buy one of each console to play the games I like. Usually I can find these games on PC, so it works out well.
-
Wanna get rid of legacy? Then get rid of Parallel/Serial/PS2 ports, and you will have my attention. MS will find a hard sell with WinXP, and they know. Sure, it's faster than Win9x if you compare them to each other on a fairly strong box (P3-class and up?), but the thing you have to remember is that Win9x is PAID FOR by those users. Win95 made a huge splash at first, and so did Win98 (because most consumers still had the non-rev/rev "A" version of the OS and wanted "out" badly!) in its debut. I just don't see that happening with XP for a while. Couple that with the incessant need by MS to sell their stupid "Plus" add-on (add-on my a$$, should be included since they included so much other $hit) and nobody will bother with it. Over time, people will see it on new computers and may decide to upgrade later (upgrade as in buy another PC more than likely) and the slow death of "legacy" apps will begin. So in short, don't hold your breath.
-
I have been a fan of FrontPage for functions like this, but I have never been a fan of using FrontPage Extensions on the server (v2002 is out, and it seems more solid and quicker than previous versions tho) unless I need to as in the case of Visual Interdev. It's very easy to get around in, and people can be up and running in minutes. Now, I have gone to Adobe GoLive! 5, and I have the HR guy using it now. It's really easy, writes slimmer, trimmer code and was pretty cheap (less than $150US) for the competitive upgrade from all the free versions of FrontPage 98 that we have with our NT 4.0 Server CDs. If any of them have used Photoshop, they can pick up on this really quickly. Plus, if they are using Photoshop and Image Ready, they can save GoLive! code in their work and GoLive! will then allow for further tweaking of various behaviors (such as mouse-overs and the like) that can be defined in Image Ready.
-
NetBEUI isn't routeable, and yep it's pretty fast. I just found it easier to focus on TCP/IP only since I didn't have to mess with Novell for the last few years. I used NetBEUI to separate the traffic between the MS peer-to-peer network and the client/server connections of the workstations to the Novell servers. Also, 15 isn't an absolute limit, but rather my self-imposed limit on that protocol at the time.
-
Personally, I like IIS. I don't have any problems with it, but then again I stay on top of updates, and use the utilities (like URLScan) that MS provides to block these exploit attempts that make the headlines. The bottom line is that IIS is easy to install and get running, so it takes a much less skilled person to maintain it. Therefore, almost anybody with NT/2K can have it running (sometimes on accident) and not have enough experience to realize they should be maintaining it. If *nix was more popular, then you would see more exploits for that platform than you do now. When I first started researching hacking 5-6 years ago, it was almost exclusively limited to getting into Unix systems, and there were plenty of exploits for them. Now, nobody seems to remember that anymore and it's easier to claim that MS writes poor code, and makes it super easy to hack anything they make. When you're that big, it's just hard to duck away from attack. I am hoping that MS will make the default settings so strict on these newer OSs, that in order to even use them you have to be somewhat experienced in configuring systems in general (be it the OS, web services, etc) and that this will help filter out the casual user that just wants to install it and see what it does from the power user or seasoned admin that knows exactly what he/she wants to do. IIS has made it much easier to bring out dynamic sites via ASP and ADO, that use common syntax forms amongst various programming platforms. It also makes searching the local server much more powerful via Index Server (yep, another exploit if not properly maintained) which can also be used for internal document control. Overall, it works really well, but like anything that's "online", you have to stay on top of it.
-
Clearing page file at shutdown option
clutch replied to Ron_Jeremy's topic in Customization & Tweaking
Nice post Greg. -
Ways to make XP Pro more responsive
clutch replied to shassouneh's topic in Customization & Tweaking
Hell, if he could use run-of-the-mill SDRAM DIMMS, I would just replace all of the memory if need be and max out the board with RAM. -
Clearing page file at shutdown option
clutch replied to Ron_Jeremy's topic in Customization & Tweaking
Well damn ghayes, took ya long enough to get here! -
OK, I think I see what you are aiming for, but... 1. The console market has been used to not having patches for so long (and since there are quite a bit of console developers looking at the XBox) I would imagine that the XBox would have to work in the same vein. But then again, my original comment was aimed at support of the unit, and if there are going to be patches then that's just one more reason not to bother... 2. Why would I want a car adapter? Are the prices of the TV and Console adjusted for this item as well? 3. Basically, with the cost of the console (to cover the cost of a broadband adapter since there is a perceived *need* for patches, not to mention a monthly fee for Internet or network access to GET the patches in the first place) then the PC would be more attractive. Not to mention that it can do more than play the 20 games or so that's available (as per your comment on the Sega platforms). 4. Covered in "3". 5. Aren't those hacked and clipped so a regular CD can be used? Or are they, in fact, complete and in tact? Personally, I make backups of every CD that I get (at work and at home) since I have had a couple get scuffed for one reason or another (or just plain lost). I just use the burn, install from that, and keep the master in the box that the software came in. If you can do complete backups on your games for the DC (or PS2 or XBox, since those are the more recent platforms we would be working with) then I would look at it further. Oh, and what would you backup the DC games with anyway? A PC? Hmmm... 6. Just get the PC and dual boot, the DC cannot and will not ever do as much as a PC, yet its cost with all of the "optional" (read: needed) hardware is running rather close to that of a PC. Plus, the DC is the only one that can do this, right? However, you did mention that you only wanted to play games on the console, right? 7. The difference is, that you can play MP for pretty much any game anytime you want, without having to wait for people to come over (or you dragging your console/controller set to their place). Plus, MP gaming on the 13" portable that you spoke would be just plain ridiculous (kinda hard to hide from the enemy when he/she is sitting right next to you). Also, MP gaming on console can really slow down an already resource intensive game (how does q3a run in 4 way deathmatch? Not that I care, since I play with 8 or more peeps at a shot anyway). BUT, sniping/camping does become much harder, so there's one selling point... 8. The nForce chipset will more than likely run like a GeForce MX at best (and is currently performing at lower than expected levels in current silicon). I would still imagine that the GF3 would be used. But if not, that PC sure is getting more attractive... 9. What can you upgrade on a console that is so much easier than a laptop? Memory? HD (oh, sorry, prolly don't have one of those do ya? )? OS? CPU (Can you upgrade one of those in a console?)? 10. As a doorstop, absolutely! I was a console fan, but I got tired of how easily the platforms would get changed and you would simply lose support for it. Technology is simply moving too fast (which is a good thing) to ask developers to keep working on outdated platforms.
-
The perception of security with respect to IPX/SPX is deceiving, and I'll tell you why. Basically, who cares about IPX/SPX? While it *is* routable (and you have to know what you are doing with it and TCP/IP networks running in parallel), any network worth getting in to would more than likely be using TCP/IP. Also, how many script kiddies/hackers/"1337" 12-year olds with too much time on their hands would know anything about that old protocol? It is broadcast based, but was a bit more resistant to "storming" on networks (but did have more network and system overhead) and was indeed, routable. Its level of security is almost synonymous with the "security by obscurity" method that NAT/PAT employs by "hiding" the workstations behind a single IP, and blocking direct access to machines unless the ports are explicitly forwarded. Now, they call it a "firewall", when in fact it isn't. The observation of packet blocking is merely a by-product of the intended design to share a single IP for many machines. Basically, with IPX/SPX, it's "security by limitation" as it's outdated and not really used for anything that most people would care about. There, nice and long-winded...
-
Ways to make XP Pro more responsive
clutch replied to shassouneh's topic in Customization & Tweaking
"Speed is money, so how fast do you wanna go?" -
My turn... W2K-1 (Main box) Win2K Pro, SP2 P3 933@1085, 1.75v (155x7, runs at 29*C at idle, and 41*C while gaming) Vantec CCK-7035D HSF ASUS CUSL2 i815 512MB Crucial CAS2 PC133 RAM WD 40GB ATA-100 HD Samsung 5x DVD/32x CD Drive Hercules Geforce 2 Pro, 64MB (Detonator 21.81) Creative SBLive! MP3+ Intel Pro/100 Mgmt Adapter Radius 19" Monitor (Trinitron AG CRT) MS Natural Keyboard Pro MS Intellimouse Explorer SanDisk USB Compact Flash Reader Nikon CoolPix 800 Digital Camera W2K-3 (Secondary Workstation) Win2K Pro SP2 Celeron 300a@450 (100x4.5, yeah, a classic...) ASUS P3B-F 256MB Generic PC133 RAM IBM 25GB ATA-66 HD 48X Memorex CD-ROM HP 9100 8x4x32 CD-R/W ATI All-In-Wonder Pro AGP, 8MB Creative Soundblaster AWE64 Intel Pro/100 Mgmt Adapter Digiview 17" Monitor MS Natural Keyboard MS Intellimouse Pro Server-1 Win2K Adv Server, SP2 Slot 1 P3 550 768MB Crucial CAS2 PC133 RAM ASUS P3B-F Maxtor 6GB ATA-33 HD IBM 20GB ATA-66 HD WD 40GB ATA-100 HD Matshita 32x CD-ROM Intel Pro/100 Mgmt Adapter Generic KB, Trackball, and Monitor (usually not used, as most tasks are handled via Terminal Services) Server-2 Win2K Server, SP2 Celeron 333 Diamond Micronics C400 (Intel BX-based board) 256MB Generic PC133 RAM Maxtor 20GB ATA-100 HD Acer 50x CD-ROM Intel Pro/100 Mgmt Adapter
-
I used NetBEUI quite a bit in the past, because I could setup servers in DOS 6.x (nifty little conversion for "net.exe" from MS, it was "WG1049.exe" and would permit the ability to share folders and printers) that would host our telephony cards. The speed was due to its small nature, and low memory requirements. You would also see that it has a bit slimmer layering in its design. Now, if you actually saw its behavior on a LAN of more than 15 workstations, you would see the collision activity that can take place using that protocol (broadcast-based protocols beat up devices quite a bit, I have seen Intel NICs die because of the abusive implementation of IPX/SPX from Novell's clients).
-
Um, actually NetBEUI is a broadcast-based protocol that can, in fact, completely saturate networks (which is why MS spec'd it later as a "small network only" protocol). As for security, in a small network that was generally a lesser concern. Now, as for performance, it was faster than IPX/SPX or TCP/IP in MS OSs when used on the same small networks and only reason why latency would have been much of an issue would be because of its use on large networks. So, spaceman pretty much nailed it with his post.
-
Do this: 1. Click Start, point to Settings, and then click Network and Dial-up Connections. 2. Click the local area connection that you want to be statically configured, and then click Properties on the File menu. 3. Click Internet Protocol(TCP/IP), click Properties, click Advanced, and then click the WINS tab. 4. Click Enable NetBIOS over TCP/IP. 5. Click OK, click OK, and then click OK. Make sure that all of the workstations have NetBIOS over TCP/IP enabled (hence, NetBIOS would be "bound" at this point) so they can broadcast to each other.
-
Do yourself a favor and stay away from IPX/SPX and NetBEUI if possible. I have used TCP/IP successfully in the majority of MS Operating Systems (DOS 6.x/W9X/NT3.51/NT4.0/W2K/XP, WFW is just a horrible, horrible memory ) without any problems between themselves and/or different versions. Now, did you make sure that NetBIOS was bound to TCP/IP so you could "see" the other machines in Network Neighborhood? Most people complain that the machines don't work with each other because they have installed TCP/IP and don't have NetBIOS bound to that protocol. Also, if you are using DHCP, you should either: A. Make sure the hosting server advises the workstations to use NetBIOS over TCP/IP B. Configure the clients independently to bind NetBIOS C. Use WINS
-
A couple of dumb questions for ya, if you don't mind. Have you tried disabling any of the background apps/services (like popup killer) before running the setup file? Have you tried reinstalling the service pack? Have you tried other admin-level logons?
-
Do you have the Active Virus Defense suite? If so, check out the current version of E-Policy Orchestrator (you have to download it, don't use the version on the CD; the version available for download is 2.0) as it works really well. Of course, I still rely heavily on SMS 2.0 to do some of the dirty work (old habits die hard) but for a unified virus management interface, it works really well.
-
Oh yeah, that was lame. I have been using 4.5.1 for a while now, and forgot all about that. Get with the times bud!!!
-
Funny, since I used to dual boot both OSs, and I had the same issue that you mentioned until I upgraded my drivers (normally the timings are hardware dependent, but for some odd reason the video card wouldn't sync the same in both OSs until I got the newer drivers).
-
Generally, that behavior is due to the difference in video drivers amongst the OS platforms. What video card are you using? Is there a version for Win2K and Win9X that has the same version number? Try using the newest drivers for both operating systems and see if that alleviates the issue.
-
I don't care for consoles too much, since they have to be connected to a TV which has a dismal resolution, and fixed refresh rate. But the XBox does show some promise. For example, one COOL thing about consoles is that the games are as bug free as they will get when released. They will have been proven to work on that combination of hardware, since that's all they have been developed/tested on. Now, the downside is that you cannot upgrade them and they are pretty much disposable technology. I think that they have their place, and I can see the attraction, I just haven't decided if I want to connect an XBox to my 45" Mitsubishi yet. Oh, and as for the breakdown from Down8: 1. I have never seen a laptop sold without an AC power convertor 2. The laptop would have better resolution than the TV 3. The console in question would be more like $300 (and probably more, if you are saddled with having to buy a gaming bundle to get the console) rather than $200. 4. The laptop would be infinitely more portable than the console/tv combo ever would be 5. The laptop would also support true multiplayer (not lame split-screen) gaming 6. The laptop would also support broadband 7. While you can't play games from a N64 on a Playstation, some of these same games have been ported to PC (or in fact, have been ported from PC) and lets the PC enjoy a larger selection of premium games 8. You could simply scrap the idea of a laptop, and buy a decent PC for $700 that will not only play games, but will do a whole helluva lot more (as brought up previously) Thank you, and good day...