topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Tuesday January 27, 2026, 9:37 am
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Recent Posts

Pages: prev1 ... 214 215 216 217 218 [219] 220 221 222 223 224 ... 246next
5451
T-Clock / Re: T-Clock 2010 (alpha - download)
« Last post by Stoic Joker on March 19, 2010, 03:01 PM »
8. Some other stuff I can't remember at the moment.
Please, sir, I want some more of that:)
-cranioscopical (March 19, 2010, 12:48 PM)
9. Additional items I can't remember - But included on request.
5452
T-Clock / Re: T-Clock 2010 (alpha - download)
« Last post by Stoic Joker on March 18, 2010, 10:01 PM »
Well, Damn the luck - Tabbing Issue was actually with Virtual PC. After I restarted the whole shebang it started working just fine.

So... Updated download above - With the following fixes/additions:

1. Deleting a running timer, also stops said timer.

2. Deleting a timer no longer scrambles all of the other configured timers.

3. Removed excess MessageBoxes (that weren't actually supposed to be there - oops!).

4. Fixed Spastic Tab Order issue.

5. Entering out-of-range time data is now auto-converted to its D:HH:MM:SS equivelents

6. Timer Status message now reflects the above (per ewemoa's formatting suggestion) - This will eventually be a "Live" counter.

7. Timers that were running on program shutdown are automatically reset so they don't get stuck as unstartable.

8. Some other stuff I can't remember at the moment.
5453
T-Clock / Re: T-Clock 2010 (alpha - download)
« Last post by Stoic Joker on March 18, 2010, 08:04 PM »
Holy Hell, Mom Was Right - If you pick at a loose thread, he whole damn thing unravels... (I'll explain later)

Yup.  As a somewhat vague example, there are these sites that make you wait before letting you do certain things, and if you miss a window of opportunity you are made to wait another period of time.  It has been my experience that the quoted wait times are often communicated in seconds.  I've seen 500 seconds wait times, FWIW.

A little more detail on what I did:

I put the focus in the seconds field, entered 100 and subsequently used tab to visit other fields, ensuring that the other time fields were 0.  From what I can see, tabbing off of the seconds field does not appear to update the time fields.  At the time when I click on the start button, what I see for time values consists of:

  0 Days
  0 Hours
  0 Minutes
  100 Seconds

If I visit the Timer dialog subsequently and copy-paste the seconds value elsewhere, I see a value of 65595.

This was actually 2 separate issues.

1. Values were being taken from the Spinner Control not the Edit Control ... So 100 being out-of-range ~ Gave the appropriate (65595) error.

2. I never thought of anybody doing that.

So... Values now taken (at face value...) from Edit Control and are then passed through here:
Code: C++ [Select]
  1. //================================================================================================
  2. //--{ DC - ewemoa }------+++--> Validate Values as Being Within Expected Ranges (Adjust as Needed):
  3. void ValidateTimerInput(int sec, int min, int hrs, int day) { // Second  = 1 Second --------+++-->
  4.                                                                                // Minute = 60 Seconds
  5.                                                                                // Hour = 3600 Seconds
  6.   if(sec > 59) {                                                           // Day = 86400 Seconds
  7.           for(sec; sec > 59; sec -= 60) {
  8.                   min += 1;
  9.           }
  10.   }
  11.  
  12.   if(min > 59) {
  13.           for(min; min > 59; min -= 60) {
  14.                   hrs += 1;
  15.           }
  16.   }
  17.  
  18.   if(hrs > 23) {
  19.           for(hrs; hrs > 23; hrs -= 24) {
  20.                   day += 1;
  21.           }
  22.   }
  23.  
  24.   if(day > 42) day = 7; // It was either Hitchhikers Guide to the Galaxy -or- the 49.7 day bugg :-)
  25. }

Now you can stick anything anywhere & it'll convert it for you on-the-fly as needed.


I noticed that if I press the X button to remove a timer without stopping it first, it still appears under the T-Clock Timers submenu.  After the timer expires, it goes away, but I guess there's no straight-forward way to get at it to stop it.  Am I missing something obvious may be?

Yes, that would be the I'm obviously not that bright, part. The extra flurry of message boxes that I'm sure you noticed were supposed to remind me (test values) I hadn't finished coding that part. The next release will include the Auto-Suicide on Delete function - That I forgot to do earlier (...Thanks for reminding me... :)).

So, do I really still need to explain the Thread Comment?

Rather bizzar side effect, when I reordered the controls in the .rc script to fix the Tab Order (which I've done many times) Tabs have now completely quit working (e.g. Key Has No Effect).


And etc. *Shrug* ...But that's enough whinning I gota get back to work ;)

Hopefully I'll have a new build ready sometime this weekend.


Thank You
5454
I believe it was Milgram's Experimentw.
Now there is a chillingly sad depiction of our society - However it does make me feel good about being a nonconformist, with a total lack of respect for authority... ;)
5455
T-Clock / Re: T-Clock 2010 (alpha - download)
« Last post by Stoic Joker on March 18, 2010, 06:18 AM »
Tab Order  :wallbash: You got me! :) I knew I was forgetting something (Using forest for the trees defense).

the dialog box that comes up says something like 18:wx:yz
format of that is hh:mm:ss so it looks like it's counting down from 18 hours.

60 - 100 seconds timer? ...I ganged all the spinner controls together so that clicking up on 59 seconds would automatically set minutes to one. So as each spinner reaches it max (or min) value, it will start updating its neighbor control.

The intent behind the design was that 60 seconds be 1 minute, and 100 seconds be 1 minute 40 seconds.

I spent a lot of time trying to work out how to do this, and didn't think enough about should I do this perhaps? I can pull that (update yer neighbor) part if it's to confusing/annoying - or try tweaking it for clarity if it's saveable.

Thanks for the input! :)
5456
T-Clock / Re: T-Clock 2010 (alpha - download)
« Last post by Stoic Joker on March 17, 2010, 09:22 PM »
Mouser - Sorry man, wasn't ignoring you, I've just been busy trying to keep the project rolling while I'm still in this window of opportunity (time wise). Most of what had been update/fixed was under the hood stuff. Biggest item being the Properties Dialog's habit of crashing the clock (and shell) any time the mouse options tab had been viewed. I should probably do a proper posting with one of the NANY release templates at some point to avoid confusion.

So... I decided to tackle the Timers part of T-Clock, as it has always kinda bugged me (OK, it was total shit to be honest... :)) While not completely finished, it is working well enough to share. The Stopwatch part (what pathetic attempt at one there was) has been temporally removed until I can do it properly (which is next). Latest updated build of T-Clock available bottom of first post in thread.

Before:
T-Clock x64 (Timers).jpg

After:
T-Clock 2010 (Timers).jpg

Multiple timers can be stopped and started from the UI (stopping a timer previously required restarting the clock), Timers can now be set for Days/Hours/Minutes/Seconds, instead of just minutes. Running timers menu now gives the names of the running timers and are click-able to open a current time remaining message. MessageBox will be replaced by a running "live" countdown eventually - but I ain't there yet. ;)

Feedback Appreciated... :)
5457
T-Clock / Re: T-Clock 2010 (alpha - download)
« Last post by Stoic Joker on March 13, 2010, 02:28 PM »
T-Clock 2010 alpha download link is (and will be) at the bottom of the first post of this thread.

Go ahead be brutal honest... ;)
5458
N.A.N.Y. 2010 / Re: NANY 2010 Release: Page Countster
« Last post by Stoic Joker on March 12, 2010, 04:01 PM »
Damn! Not sure why I didn't think of this before ... There is a smaller version of HP's (insanely bloated) Web Jet Admin, called HP Easy Printer Care. It should give you what your after for the HP stuff that's On-the-Wire - It sits in the tray, monitors the herd, and gives a Balloon Message if anything "interesting" happens.
5459
N.A.N.Y. 2010 / Re: NANY 2010 Release: Page Countster
« Last post by Stoic Joker on March 12, 2010, 02:05 PM »
The 4100 was the first model to have a toner level gauge ... and it's a bit flakey. If the printer doesn't like the cartridge's embeded chip, it will ignore it, and continue what ever it last calculated from the last chip it liked.

As far as the Email events go they're all (4000/4050/4100) to old for that.
5460
Living Room / Re: When you make your 100'th Post
« Last post by Stoic Joker on March 12, 2010, 01:57 PM »
Speaking of Evil Intent... ;)
DC Post 666sm.jpg
5461
That Jack's not a bad guy - Sticking to the code as he does... *Snicker*
5462
T-Clock / Re: T-Clock 2010 (Maybe...)
« Last post by Stoic Joker on March 06, 2010, 06:29 PM »
Okay, Just to show that I haven't dropped-the-ball...again... ;) (Here's an update)

Before:
T-Clock x64 (Mouse).jpg

After:
T-Clock 2010 (Mouse).jpg

Mouse Tab has been reorganized and I added a ListView of all currently configured mouse click options for clarity. Screen Shots were taken on my 64-bit Server 2003 Domain Controller - No crashes were experienced during testing... :)
5463
Living Room / Re: Will you miss newspapers when they're gone?
« Last post by Stoic Joker on March 05, 2010, 03:31 PM »
What's a News Paper..?   :D

The wife likes reading the Sunday paper (Damn-if-I-know-why) ...I just read the comics.
5464
T-Clock / Re: T-Clock 2010 (Maybe...)
« Last post by Stoic Joker on March 03, 2010, 07:17 PM »
f0dder - After going through and tidying up the various pointer castings TC2010 is proving to be quite stable. I've even spent some quality time trying to crash it, and happily failed. Rather odd side note is that the strange behavior of the Mouse Tab of the Properties Dialog crashing the program seems to have disappeared. So I've tentatively (also) crossed that Bugg off the To-Do list for the moment. :)

Daleus - Thank You, I truly appreciate the encouragement. I got hooked on TClock back in the late 90s and am completely incapable of parting with it. If you are interested in a bit of (alpha/) beta testing ... I could be easily coerced into posting a download of TC2010 once I get a few more things ironed out. ;)
5465
N.A.N.Y. 2010 / Re: NANY 2010 Release: Page Countster
« Last post by Stoic Joker on March 03, 2010, 07:00 PM »
Awesome piece of software!  I love it! :D  Been looking for something like this for a while.

Something I'd like to see, which might end up being a different project, is to have something sit in a system tray, or running in the background as a service, monitoring a list of printers toner and send an alert, e-mail or notification, when the toner is out or very low.  Possibly paper too.  *shrug*

Looking for a way to be preemptive on some of the things around the office. :)

Thank You, I'm glad you're enjoying Page Countster.

There is an older (tray utility) project called PrinStats mentioned on the bottom of page one of this thread that is for monitoring a single printer's page count, toner level, and display messages (which would give paper out etc.). But it's only for one printer at a time. Real time monitoring/reporting of network printers is one of the features that is planned for the complete suite that (will be a comercial product) Page Countster is part of.

Beyond that Techidave is indeed correct in that many of the newer printers feature automatic emailing of certain events.
5466
T-Clock / Re: T-Clock 2010 (Maybe...)
« Last post by Stoic Joker on March 03, 2010, 07:14 AM »
Hm, just did a silly little test - obviously won't work runtime, but compiles clean with the following two compilers (VS2008 + SP1):
Microsoft (R) C/C++ Optimizing Compiler Version 15.00.30729.01 for x64
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.30729.01 for 80x86
I'm like totally open for suggestions here. ;)

...should work fine for older compilers as well, although there is a PlatformSDK dependency to have GWLP_* work (dunno when that was introduced, but iirc it works fine on VS2005).
It does, and is used/was required to get the origional (VS2k5) project off the ground

Note that I prefer the C++ style cast operators, but C style (cast) just as well (they're less explicit and harder to grep for, though, and the C++ operators allow you to be more precise wrt. what/why you're casting).
That decision was made for me as the origional (authors) code is pure C, which I haven't changed ... But have regretted more than once...
5467
T-Clock / Re: T-Clock 2010 (Maybe...)
« Last post by Stoic Joker on March 03, 2010, 06:02 AM »
What's up with having two casts (ie., (LONG)(LONG_PTR))? A single (LONG_PTR) ought to suffice
...Ought to, being the operative part :) ...But results in:
warning C4244: 'function' : conversion from 'LONG_PTR' to 'LONG', possible loss of data

However, Originally I was using a single Line of code for both (e.g. no compile time switching), so I needed to get that single line to work on/for both the 32 & 64 bit versions ...(and I insist on the code compiling with zero errors or warnings)... Which is I think how I landed there. Did I mention that this (or rather that 4 year ago project) was my baptism by fire in the pointer casting department.

I did some quick testing and now have:
Code: C++ [Select]
  1. oldWndProc = (WNDPROC)(LONG_PTR)GetWindowLongPtr(hwndClock, GWL_WNDPROC);
  2. //==================================================================================
  3. #if defined _M_IX86 //---------------+++--> IF Compiling This as a 32-bit Clock Use:
  4.   SetWindowLongPtr(hwndClock, GWL_WNDPROC, (LONG)(LRESULT)WndProc);
  5.  
  6. //==================================================================================
  7. #else //-------------------+++--> ELSE Assume: _M_X64 - IT's a 64-bit Clock and Use:
  8.   SetWindowLongPtr(hwndClock, GWL_WNDPROC, (LONG_PTR)(LRESULT)WndProc);
  9.  
  10. #endif
  11. //==================================================================================
  12.  SetClassLong(hwndClock, GCL_STYLE, GetClassLong(hwndClock, GCL_STYLE) & ~CS_DBLCLKS);

...Which works on both 32 & 64 bit test machines. I could try running a few tests with just (LONG_PTR)(LRESULT) for both after work if you think it would be cleaner, but for now I'm just glad to be done abusing my server.

Only x64 machines I have are my main (Win 7) dev machine and my (Win 2k3 R2) domain controller. Repeatedly crashing the shell on the dev machine makes it impossible to keep my notes in order ... So I've been torching the shell over & over via Terminal Services for the last few days on the Domain Controller. Which says a lot for TS as in over 100+ shell hangs/crashes the original session never disconnected once and the box is still stable.

Disclaimer: (Kids do not try this at home) This is not considered a good practice or even recommended behavior... (It's actually rather stupid) ;)
5468
T-Clock / Re: T-Clock 2010 (Maybe...)
« Last post by Stoic Joker on March 02, 2010, 06:46 PM »
ouch, thats a tricky one.

Quite true, but it was at least almost (but not quite) twice as much fun as trimming your toenails with a chainsaw... :)

But seriously... Being that I have multiple project files pointing at the same source pool, the 32-bit compile complained about the pointer conversion (might cause data loss (yada, yada, yada...)). So I had to make it conditional at compile time, which ends up being this:
Code: C++ [Select]
  1. oldWndProc = (WNDPROC)(LONG_PTR)GetWindowLongPtr(hwndClock, GWL_WNDPROC);
  2. //==================================================================================
  3. #if defined _M_IX86 //---------------+++--> IF Compiling This as a 32-bit Clock Use:
  4.   SetWindowLongPtr(hwndClock, GWL_WNDPROC, (LONG)(LONG_PTR)WndProc);
  5.  
  6. //==================================================================================
  7. #else //-------------------+++--> ELSE Assume: _M_X64 - IT's a 64-bit Clock and Use:
  8.   SetWindowLongPtr(hwndClock, GWL_WNDPROC, (LONG_PTR)(LRESULT)WndProc);
  9.  
  10. #endif
  11. //==================================================================================
  12.  SetClassLong(hwndClock, GCL_STYLE, GetClassLong(hwndClock, GCL_STYLE) & ~CS_DBLCLKS);

Which compiles cleanly (no errors or warnings) and runs without crashing on both 32 & 64 bit test machines.
5469
T-Clock / T-Clock 2010 (download)
« Last post by Stoic Joker on March 02, 2010, 06:14 PM »
Stoic Joker's T-Clock 2010

Application Name T-Clock 2010
VersionBuild 95
Short Description Highly Configurable Taskbar Clock
Supported OSes  Windows 2000/XP/2003/Vista/2008/7 32 & 64 bit
Web Page www.StoicJoker.com/TClock for general info. Download is still only available here.
Download Link * T-Clock 2010 (build 95).zip (703.66 kB - downloaded 85165 times.)
Download Link * T-Clock.20130503.f9f71075.7z (800.47 kB - downloaded 19825 times.) This is LonelyPixel's build containing Henriko's Week Number fix
Download Link White Tiger's GitHub Release Page
System Requirements
  • Win2k or Higher
  • Memory 512K
Version History
  • See Below
Author Stoic Joker - Has officially closed the project as of Saturday March 10, 2012
Source Code Stoic Joker's Last (unreleased) Build 98 and then...
Author WhiteTigX - Grabbed the released source code and reopened the project about a year later
-+-
LonelyPixel's GitHub Source Code Repository
-+-
White Tiger's GitHub Source Code Repository


Description
The Original TClock written by Kazubon in the early 90's was a popular classic that was on the edge of extinction when Windows started going 64bit. ...I simply chose not to let that happen.

Features
The Application's features.

Planned Features
Currently Open for Suggestions.

Screenshots
Screenshots of the Application.

Usage
Installation
Extract the .zip file (where you like) & run the program.

Using the Application
Hopefully this is all covered in the help file.

Uninstallation
Close Program & delete it.

Known Issues
Currently None - But I have faith that you guys will find something wrong with it... ;)

Version History
Build 95 - Fixed Middle mouse button, and added the following features:
  • PC Speaker alarm beep option (.pcb files)
  • Locking Workstation Turns Off Monitor(s) (I Just Had to Try Doing This)
  • System first week of year (used by popup calendar) adjustable via GUI
  • Popup calendar options for 1, 3, or 12 month view (still needs work but is there)
  • Added always on top option for calendar
  • Added display am/pm as a/p, A/P, and  /p options
Build 90 - Added Font Quality option to resolve the Fuzzy Font Bugg, and Bouncing Alarm windows. (details)
Okay... It's 12/23/2010, So I either have to either release this thing or change the name.
Beta 8.5 Windows 2000 Support Returns! - Thanks to MSVS2008
Beta 8 ... Same as first 8 Just repacked properly - Not a clue how I screwed that up.
Beta 8 - End of High DPI Dialog Position Bugg (also added build # to About Tab)
Beta 7.5 - Fixed Logic Error which caused Alarm AM/PM setting to be ignored.
Beta 7.4 - Added Display (ISO) Week Numbers on Calendar Option, Close Calendar on Lose Focus Option, Calendar Dialog now dynamically resizes at runtime if/as needed (toggle Week Numbers to see), Added Miscellaneous Tab to Properties Dialog to Adjust Above.
Beta 7.3 - Added Option to have Alarm Ring X Times
Beta 7.2 - Added Option to have Alarm Chime the Hour.
Beta 7.1 - More Fun with the Alarm Tab Crash Bugg
Beta 7 - Rework of Alarms Page Control behavior & etc... (see thread for details)
Beta 6 - This is a rough draft of the requested Time Synchronization feature (details to follow).
Beta 5.5 - More mucking about with the infernal Hotkeys (which should finally be be nailed down at this point)
Beta 5.2 - Fixed Loss of (HotKey) Focus Bugg
Beta 5 - Now with configurable HotKeys (I'm way to tired to post details)

Revised request for Ordinal Date Added (two ways) and also added Day-Of-Year.
OD = Ordinal Date UTC
Od = Ordinal Date Local
DOY = Day of Year in (001 - 366) Decimal format.

Help file has been updated with new options - but it looks like hell
Found this request for the Julian Date in an Email, so I tossed it in (Formatting Option JD)
Added Hotkey Options for Stopwatch, Add/Edit Timers, & Timer Watch dialogs

6. The Properties Dialog Mouse Tab Crash Bugg is gone - Thanks to a T-Clock fan that (also happens to be a programmer) has been working with me via Email for the past few weeks.

5. There is an EasterEgg of sorts for the Win2k folk that (is easy to find in the registry) allows TC2010 to make the Desktop Icon Text Labels transparent.

4. Registry info structure has been modified slightly (Simplicity/Testing purposes) so TC2010 will not use/modify the TC3 configuration data.

3. Taskbar transparency has been brought back because (Um...) it seemed like the thing to do at the time. It has been tested and works on all the above.

2. It is stable, and has been tested on Win2k/XP/Server2k3 x64/7 x64 without any Shell hangs/crashes/etc.

1. Okay, so I finally managed to end up with something stable enough to share with the rest of the class ... There are a couple of things to be noted however: This is alpha so it ain't perfect.

Okay, So I've been trying to get this project back off the ground for a few years ... and as of late ... That's really been starting to bug me. Missing source code issues aside ...(long story documented elsewhere)... I still had the partially branded project file from the web server to work with. That copy however (actually all of them in retrospect...) had an issue with MSVS 2005 SP1, which caused a quite consistent shell crash on load. I confirmed this by compiling the code with MSVS 2005 (no service packs) and it did indeed run just fine. Hence the conclusion that either SP1 or something that SP1 didn't like about my code was the culprit.

I have spent the better part of the last 3 days hammering on this in an attempt to render that particular bugg nice and dead. I have succeeded. Hence (in a mild fit of artistic rage...) I have decided to display said buggs still twitching carcase here ... on the odd chance that someone may need to drive a similar stake through one of its cousins:
Code: C++ [Select]
  1. oldWndProc = (WNDPROC)(LONG_PTR)GetWindowLongPtr(hwndClock, GWL_WNDPROC); // The x64 Bugg Was Here
  2.   // SetWindowLongPtr(hwndClock, GWL_WNDPROC, (LONG)(LONG_PTR)WndProc); <--+++----<<<<< FAIL Code!!!
  3.   SetWindowLongPtr(hwndClock, GWL_WNDPROC, (LONG_PTR)(LRESULT)WndProc); //----+++--> This Fixed IT!!
  4.   SetClassLong(hwndClock, GCL_STYLE, GetClassLong(hwndClock, GCL_STYLE) & ~CS_DBLCLKS);

Will TC2010 make it to release? I don't know. But this is a hell of a lot closer to a good start then I've been in the past 4 years.

 :D
-Original Post
5470
Living Room / Re: Strange question about salsa
« Last post by Stoic Joker on March 02, 2010, 03:49 PM »
What the heck is in store bought salsa that makes it spark when microwaving it?

The merciless peppers of Quetzlzacatenango?

 :huh: ...Okay, I dare you to say that three times fast.
5471
Living Room / Re: When 40%-Off Your Total Purchase Becomes 0.3%-Off
« Last post by Stoic Joker on March 01, 2010, 03:33 PM »
Coupons frequently have something to the effect of "Not valid in combination with any other offers" in extremely fine print on them somewhere. Which is understandable (kinda) to a point. but, I wouldn't call it greedy on your part, because I'd take the same shot hoping it would work.
5472
Nuance is also good, but definitely not in the "fast" category as far as starting up.  Once in the application, it behaves quickly.  To me, speed is two different issues:  startup speed, and operating speed.  Nuance is great for operating speed.  Also, nuance has nice layout features and powerful editing features.  But I wouldn't use it for my viewer.
Hm... I've been toying with trying out the Free Nuance Reader - When you say it's slow, do you mean slower than Acrobat? ...or just "regular" slow?
5473
Living Room / Re: Fixed my network - The Hard Way
« Last post by Stoic Joker on February 28, 2010, 01:28 PM »
IceSword looks interesting - But it appears to have fallen off the planet back in 2007. Is the Project/Author still active?
5474
Developer's Corner / Re: What do YOU do to keep your head cold when coding?
« Last post by Stoic Joker on February 26, 2010, 06:48 AM »
I smoke, I've done so for years, and it works well for me - Sit back, have a smoke, relax, & keep going. Much unlike the alternatives, smoking doesn't make you suicidal ... Which is why I maintain that cigarettes are much better for your health than anti-depressants. ;)
5475
Circle Dock / Re: UAC Issues - Vista/Windows 7, 32 & 64-bit
« Last post by Stoic Joker on February 25, 2010, 07:12 AM »
As for 64-bit OS's my experience is somewhat limited - to less than one week. What I can say is that I'm unable to use Visual Studio 2008 on that platform to actively develop CD as should I try to load the Main Settings dialog, Visual Studio crashes with an "out of memory" fault (and that's on a 4GiB machine). Instead I use a 2GiB 32-bit machine and that same dialog loads faultlessly (and with oodles of memory to spare). So, from my experience, running 32-bit applications on a 64-bit platform is not ideal hence my decision to release a 64-bit version of CD.
That is odd, as I'm still heavily using VS 2005 on Win7 x64 on a daily basis and it's never blinked. Both T-Clock32 & x64 were developed with VS 2005 on Vista x64 (back when), using two different project files that pointed at the same source pool.

As for 64-bit applications requiring more memory, you're probably correct however the extra amount of memory CD-64 requires (over CD-32) is negligible but CD-64 does seem considerably more responsive than CD-32 on either a 32-bit or 64-bit platform (assuming the CPUs are of equivalent speed).
I keep reading this (assuming I'm missing something) wondering how you're getting CD64 to run on a 32-bit platform - That's not supposed to be possible.

Side note: The only reason I had to create T-Clock x64 (which does use quite a bit more memory) was because of the Clock Window Shell Hook (injecting 32-bit hook into 64-bit process no worky), other then that it could have stayed 32-bit and been fine. (...Well except for the 9x era hardware access code that had to be stripped out for Vista).
Pages: prev1 ... 214 215 216 217 218 [219] 220 221 222 223 224 ... 246next